cost-booster-route

Routes tasks through hooks_route and reports Tier 1 Agent Booster bypass utilization.

70.1k|8.4k|Updated Jun 2, 2025
One-click install
npx skills add https://github.com/ruvnet/claude-flow --skill cost-booster-route
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cost-booster-route
Source: https://github.com/ruvnet/claude-flow/tree/main/plugins/ruflo-cost-tracker/skills/cost-booster-route
Command: npx skills add https://github.com/ruvnet/claude-flow --skill cost-booster-route

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams running LLM-based coding agents often pay Sonnet/Opus prices for simple code transforms that could run as zero-cost WASM transforms. This Skill reveals how much of your task batch qualifies for the $0 Tier 1 Agent Booster path so you can measure and reduce unnecessary LLM spend.

Core Features & Use Cases

  • Batch task routing: Sends up to 50 task descriptions through the 3-tier hooks_route router and captures each classification response.
  • Tier partitioning: Splits tasks into Tier 1 (Agent Booster, $0 WASM transforms) versus Tier 2/3 (LLM) based on the [AGENT_BOOSTER_AVAILABLE] marker, and extracts model recommendations.
  • Cost reporting and persistence: Computes upper-bound spend for LLM-routed tasks, prints a bypass utilization report, and stores results in the cost-tracking memory namespace for cost-report.
  • Use Case: When cost-report shows Sonnet spend on tasks like var-to-const or add-types, run this Skill on recent task descriptions to confirm how many could have bypassed the LLM entirely.

Quick Start

Run the cost-booster-route skill with --from-recent to analyze my recent task descriptions and show how many qualify for zero-cost Agent Booster routing.

Frequently Asked Questions about cost-booster-route

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check which tasks qualify for zero-cost Agent Booster routing?

Run this Skill with a task description or --from-recent to pull recent entries from cost-tracking memory. It routes each task through hooks_route and reports how many returned the [AGENT_BOOSTER_AVAILABLE] marker, which indicates a $0 WASM transform path.

What is the 3-tier model routing in claude-flow?

The 3-tier router classifies tasks into Tier 1 (Agent Booster WASM transforms with no LLM call), Tier 2, and Tier 3 (LLM-backed execution). Tier 1 handles simple transforms like var-to-const, add-types, add-error-handling, async-await, add-logging, and remove-console.

How many tasks can I analyze in one batch?

The batch is capped at 50 tasks per run. You can supply a single task description as an argument or use --from-recent to collect recent entries from the cost-tracking memory namespace via memory_search.

Why does the Tier 1 count seem lower than expected?

The [AGENT_BOOSTER_AVAILABLE] marker only fires when the upstream router populates the agentBoosterIntent type, and the published CLI's semantic VectorDb path does not always trigger the classifier. Treat the reported Tier 1 partition as a lower bound on actual eligibility.

Does this Skill verify the claimed 352x speedup of Agent Booster?

No. The sub-1ms latency and $0 cost are structural properties of WASM transforms, but the 352x speedup is an upstream claim not yet verified by this Skill. It reports what the router actually returns rather than validating benchmark claims.