Skill Introduction

Overview

Export cost-tracking telemetry in Prometheus textfile or webhook JSON formats — for external observability (Grafana, Datadog, custom dashboards)

Core value

Turns reusable Debugging know-how into an installable skill, helping users complete github, community work faster.

Target users

Developers, testers, and maintainers who handle Debugging tasks in Focus Code.
Teams that already trust workflows or content from ruvnet.
Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

Read the skill content first to confirm required inputs, expected outputs, and dependencies.
Try it on a small task before relying on it for critical work.
Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

Tasks related to github, community that need a reusable execution flow.
Converting a community repo, team convention, or personal workflow into day-to-day assistance.
Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

Results depend on the quality of the original skill content and may need human correction.
It does not replace code review, tests, security review, or professional judgment.
External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

Structured around Debugging, making it easier to discover and reuse than loose prompt snippets.
Marked as GitHub, which helps users judge trust and maintenance expectations.
Keeps the original source link available for repository, documentation, or discussion follow-up.
Tagged with github, community, so it can be filtered by concrete task intent.

Install and use

Install

Copy Install Command

focus install cost-export-dc26b2

View source

Detail Preview

SKILL.md

Primary filemarkdown3 KB

name: cost-export description: Export cost-tracking telemetry in Prometheus textfile or webhook JSON formats — for external observability (Grafana, Datadog, custom dashboards) argument-hint: "[--prometheus <path>] [--webhook <url>]" allowed-tools: Bash

Cost Export

Pulls every session-* and budget-config-* record from cost-tracking and emits in formats consumable by external observability systems. Without this, cost data lives only inside the AgentDB namespace; with it, the same data lights up dashboards.

When to use

After any cost-track run, to refresh metrics for Grafana / Datadog / Prometheus.
Cron-friendly via /loop 5m to keep external dashboards near-real-time.
One-shot to a webhook for ad-hoc reporting (Slack, custom endpoint).

Steps

Pick a format — textfile collector for Prometheus / Grafana, or webhook POST for everything else:

# Prometheus node_exporter textfile collector
node plugins/ruflo-cost-tracker/scripts/export.mjs --prometheus /var/lib/node_exporter/textfile_collector/cost_tracker.prom

# Webhook (POSTs JSON; add auth via env)
EXPORT_WEBHOOK_HEADER='Authorization: Bearer $TOKEN' \
  node plugins/ruflo-cost-tracker/scripts/export.mjs --webhook https://hooks.example.com/cost-tracker

# Stdout JSON (default if no flag)
node plugins/ruflo-cost-tracker/scripts/export.mjs

Inspect what's emitted — Prometheus output includes:

cost_tracker_total_usd                                    <gauge>
cost_tracker_tier_total_usd{tier="opus|sonnet|haiku"}     <gauge>
cost_tracker_session_total_usd{session="<8-char>"}        <gauge>
cost_tracker_session_messages{session="<8-char>"}         <counter>
cost_tracker_budget_usd                                   <gauge>  (if budget configured)
cost_tracker_budget_utilization                           <gauge>  (spent / budget)

Webhook payload shape — the JSON the webhook receives matches the stdout JSON: { exportedAt, sessions: [...], budget, totalUsd, byTier }. Headers may be added via EXPORT_WEBHOOK_HEADER='K1: V1, K2: V2' (comma-separated).

Env overrides

Env	Default	Purpose
`EXPORT_NAMESPACE`	`cost-tracking`	Override target namespace
`EXPORT_WEBHOOK_HEADER`	unset	Comma-separated `K: V` pairs for webhook auth
`EXPORT_QUIET=1`	unset	Suppress non-error confirmation output

Cross-references

cost-track — produces the data this skill exports
cost-budget-check — the same cost_tracker_budget_* metrics are alertable in Prometheus
node_exporter textfile collector docs (Prometheus convention) — drop the .prom file in the collector directory and Prometheus picks it up

cost export