Cost Export
- 587 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
cost-export is an agent skill that exports ruflo cost-tracking session and budget records to Prometheus textfile or webhook JSON for Grafana, Datadog, and custom observability dashboards.
About
cost-export is a ruflo agent skill that pulls every session-* and budget-config-* record from the cost-tracking AgentDB namespace and emits Prometheus textfile or webhook JSON for external observability. Without export, cost data stays inside AgentDB; with it, the same telemetry feeds Grafana, Datadog, or custom dashboards. Run it after cost-track sessions or on a cron via /loop 5m to keep external metrics near real-time. Arguments accept --prometheus <path> for textfile collector output and --webhook <url> for JSON push. The skill uses Bash and fits teams operating AI agent fleets who need budget visibility outside the ruflo runtime.
- cost-export
Cost Export by the numbers
- 587 all-time installs (skills.sh)
- +10 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #680 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill cost-exportAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 587 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you export agent cost metrics to Prometheus?
Use cost-export for development tasks
Who is it for?
Teams running ruflo agent cost-tracking who need session and budget metrics in Grafana, Datadog, or Prometheus outside AgentDB.
Skip if: Projects without ruflo cost-tracking data or teams needing cloud billing exports from AWS Cost Explorer instead of agent session telemetry.
When should I use this skill?
Agent cost data must appear in Grafana or Datadog, or after a cost-track run when external dashboards need refreshing.
What you get
Prometheus textfile metrics, webhook JSON payloads, and refreshed external dashboard series for agent session costs
- Prometheus textfile metrics
- Webhook JSON payload
- Dashboard-ready cost series
By the numbers
- Exports session-* and budget-config-* record types from cost-tracking AgentDB
- Supports Prometheus textfile and webhook JSON output formats
Files
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 5mto keep external dashboards near-real-time. - One-shot to a webhook for ad-hoc reporting (Slack, custom endpoint).
Steps
1. 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.mjs2. 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)3. 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 exportscost-budget-check— the samecost_tracker_budget_*metrics are alertable in Prometheus- node_exporter textfile collector docs (Prometheus convention) — drop the
.promfile in the collector directory and Prometheus picks it up
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kHow it compares
Use cost-export when ruflo AgentDB already tracks sessions; use cloud FinOps tools when the source of truth is AWS or GCP billing APIs instead.
FAQ
What data does cost-export pull?
cost-export reads every session-* and budget-config-* record from the ruflo cost-tracking AgentDB namespace. It formats that telemetry as Prometheus textfile output or webhook JSON for external systems.
How do you run cost-export on a schedule?
cost-export supports cron-style refresh via /loop 5m after cost-track runs. Pass --prometheus <path> for textfile collector files or --webhook <url> to push JSON metrics to Grafana, Datadog, or custom endpoints.