Cost Booster Route
- 594 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
cost-booster-route is a Claude Flow routing skill that classifies development tasks through hooks_route, partitions work by Agent Booster eligibility, and reports Tier 1 WASM bypass utilization at $0 cost for developers
About
cost-booster-route is a Claude Flow agent skill that wraps mcp__claude-flow__hooks_route to route batch development tasks through a 3-tier router and surface how many jobs qualify for Agent Booster Tier 1. Tier 1 bypasses execute as WASM transforms with no LLM call, structurally $0 cost, while higher tiers still use Sonnet or Opus when needed. The skill accepts a task description or --from-recent flag and can cross-check prior routing via memory_search and memory_list. Developers reach for cost-booster-route before running similar task batches or when cost-report shows Sonnet or Opus spend on simple, repeatable descriptions that should bypass the model.
- cost-booster-route
Cost Booster Route by the numbers
- 594 all-time installs (skills.sh)
- +6 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #667 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-booster-routeAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 594 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you route agent tasks to minimize LLM cost?
Use cost-booster-route for development tasks
Who is it for?
Developers running Claude Flow agent batches who want measurable Tier 1 bypass utilization before paying for Sonnet or Opus on repetitive tasks.
Skip if: Developers not using Claude Flow hooks_route, Agent Booster, or WASM Tier 1 routing who only need one-off LLM prompts without cost partitioning.
When should I use this skill?
A developer is about to run a batch of similar agent tasks or cost-report shows high Sonnet or Opus spend on simple repeatable descriptions.
What you get
Tier classification report, Tier 1 bypass utilization metrics, and routed task execution plan
- Tier classification report
- Tier 1 bypass utilization metrics
By the numbers
- Routes tasks through a 3-tier router with Tier 1 Agent Booster WASM bypass at $0 cost
Files
Cost Booster Route
Wraps mcp__claude-flow__hooks_route and reports how many tasks the 3-tier router classified as Agent Booster (Tier 1) eligible. Tier 1 bypasses run as WASM transforms — no LLM call, structurally $0 cost.
When to use
Before a batch of similar tasks, or when cost-report shows Sonnet/Opus spend on descriptions that look like simple transforms (var-to-const, add-types, add-error-handling, async-await, add-logging, remove-console).
Steps
1. Collect tasks — single arg or recent entries from cost-tracking via memory_search. Cap batch at 50. 2. Route each — call hooks_route with the description; capture the full response string. 3. Partition — group by whether the response contains the literal [AGENT_BOOSTER_AVAILABLE] (Tier 1) vs. not (Tier 2/3). Extract [TASK_MODEL_RECOMMENDATION] Use model="X" when present. 4. Compute spend — Tier 1 partition: $0. Tier 2/3 partition: per-task upper-bound from REFERENCE.md pricing × recommended model. 5. Report
=== Booster bypass report ===
Tasks analyzed: 50
Tier 1 (booster): 18 (36%) — $0.00
Tier 2/3 (LLM): 32 (64%) — $X.XX (upper-bound)
Booster intents: var-to-const (8), add-types (5), remove-console (5)6. Persist — memory_store --namespace cost-tracking --key "booster-route-$(date +%Y%m%d-%H%M%S)" --value '{"tier1": N, "tier2_or_3": M, ...}' so cost-report picks up the tier signal.
Caveats — claimed upstream, not yet verified
[AGENT_BOOSTER_AVAILABLE]fires only when the upstream router populatesrouteResult.agentBoosterIntent.type(v3/@claude-flow/cli/src/mcp-tools/hooks-tools.ts:1228). The published CLI's semantic-VectorDb path does not always trigger the classifier — treat the partition as a lower bound on Tier 1 eligibility.- CLAUDE.md root claims
<1mslatency and352× fasterthan LLM.<1msand$0are structural;352×is claimed upstream, not yet verified here. Report what the router actually returns. - See
docs/benchmarks/0002-baseline.mdfor the full upstream-claims-vs-measured table.
Cross-references
ADR-0002 Decision #1 · ruflo-intelligence ADR-0001 §"Neutral" (closes the routing-outcomes loop via cost-optimize step 8) · CLAUDE.md root §"3-Tier Model Routing (ADR-026)".
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
Pick cost-booster-route over generic cost-reporting when you need pre-batch Tier 1 routing decisions tied to hooks_route rather than post-hoc spend summaries alone.
FAQ
What does cost-booster-route do in Claude Flow?
cost-booster-route wraps mcp__claude-flow__hooks_route to classify tasks through a 3-tier router, partition work by Agent Booster eligibility, and report how many jobs qualify for Tier 1 WASM bypass at structurally $0 cost.
When should developers run cost-booster-route?
cost-booster-route fits before batches of similar development tasks or when cost-report shows Sonnet or Opus spend on simple descriptions. The --from-recent flag reuses recent task history for classification.