Cost Trend
Skill Verified ActiveRead every docs/benchmarks/runs/*.json and surface drift in win rate, latency, escalation rate, and LLM-baseline cost over time
To proactively identify performance and cost regressions in AI model benchmarks before they impact releases or production environments.
Features
- Analyzes benchmark run history
- Surfaces drift in win rate, latency, and cost
- Flags performance regressions
- Supports JSON output for further processing
Use Cases
- Before a release to check for performance regressions.
- After corpus expansion to verify older runs still perform well.
- After upgrading agent frameworks to identify latency or strategy changes.
Non-Goals
- Running benchmarks; it only analyzes existing results.
- Detecting regressions not captured in the `*.json` files.
- Providing real-time monitoring; it's for historical analysis.
Installation
First, add the marketplace
/plugin marketplace add ruvnet/ruflo/plugin install ruflo-cost-tracker@rufloQuality Score
VerifiedTrust Signals
Similar Extensions
Benchmark
100Performance regression detection using the browse daemon. Establishes baselines for page load times, Core Web Vitals, and resource sizes. Compares before/after on every PR. Tracks performance trends over time. Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals", "bundle size", "load time". (gstack) Voice triggers (speech-to-text aliases): "speed test", "check performance".
V3 Performance Engineer
99Agent skill for v3-performance-engineer - invoke with $agent-v3-performance-engineer
Agent Benchmark Suite
99Agent skill for benchmark-suite - invoke with $agent-benchmark-suite
Social Media Analyzer
100Social media campaign analysis and performance tracking. Calculates engagement rates, ROI, and benchmarks across platforms. Use for analyzing social media performance, calculating engagement rate, measuring campaign ROI, comparing platform metrics, or benchmarking against industry standards.
Ops Revenue
100Revenue and costs tracker. AWS spend via aws ce, credits tracker, project revenue stages. Shows burn rate, runway estimate, credits expiring.
Usage Tracker
100Track and report local Claude Code usage per request: tokens consumed, estimated cost in €, sessions, projects, and tool breakdown. Use when the user asks about consumption, credits, usage, cost per request, wants to see a report, asks why a specific request was expensive, suspects a process is consuming tokens, wants to optimize their Claude Code usage, or wants to audit tool usage by request. Also triggers on Spanish phrases: 'cuánto me está costando', 'cuántos tokens', 'consumo de hoy', 'qué petición fue cara', 'está consumiendo mucho', 'optimizar consumo', 'reporte de uso', 'ver uso', 'instalar tracker', 'hook no registra'. Commands: /usage-tracker report [hoy|semana|mes|all] [proyecto], /usage-tracker top-requests [hoy|semana], /usage-tracker install, /usage-tracker status