cost-trend
Read every docs/benchmarks/runs/*.json and surface drift in win rate, latency, escalation rate, and LLM-baseline cost over time
Best for Release teamsWorks with GitHubLow risk
⌘source
- author
@ruvnet- repo
- ruvnet/ruflo
- language
- TypeScript
★46kstars
5.1kforks
May 5, 2026
✦overview.md
Key Features
- ·Reads all persisted benchmark runs
- ·Reports first→last deltas per metric
- ·Per-run series with Sonnet/Opus baseline
- ·Flags win rate/latency regressions
- ·Configurable output format and run limit
Use Cases
- →Pre-release check for speedup drift
- →Post-corpus-expansion verification of win rates
- →Post-upgrade evaluation of latency/strategy changes
Best for
- ✓Release teams
- ✓Performance monitoring
Not ideal for
- !One-off ad-hoc benchmarks
FAQs
name
cost-trend
description
Read every docs/benchmarks/runs/*.json and surface drift in win rate, latency, escalation rate, and LLM-baseline cost over time
argument-hint:
allowed-tools:Bash
Cost Trend
The smoke gate is binary (winRate ≥ 0.80 → pass/fail). The corpus benchmarks captured over time form a curve — and curves catch regressions the gate misses (win rate slowly creeping from 100% to 85% is "still passing" by smoke but a real degradation).
This skill reads every persisted run in docs/benchmarks/runs/*.json and reports first→last deltas plus a per-run series, flagging regressions in win rate or latency.
When to use
- Before a release — check that the speedup hasn't drifted.
- After expanding the corpus — verify older runs still hit the same win rate on the new corpus they reflected.
- After upgrading
agent-booster— surface latency / strategy changes.
Steps
-
Run the trend script from the project root:
node plugins/ruflo-cost-tracker/scripts/trend.mjsOptional env:
TREND_FORMAT=json— emit JSON instead of markdownTREND_LIMIT=10— consider only the most recent N runs
-
Inspect the drift summary — first vs last on win rate, avg latency, p99, escalation rate, speedup vs Gemini.
$install
1-click copynpx skills add ruvnet/ruflo --skill cost-trendSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.