agent-booster
npx machina-cli add skill a5c-ai/babysitter/agent-booster --openclawAgent Booster
Overview
WASM-compiled code transformation engine for simple, well-defined tasks. Bypasses LLM inference entirely for pattern-matched transforms, achieving sub-millisecond execution at zero cost.
When to Use
- Simple, deterministic code transforms
- High-frequency repetitive modifications
- When latency is critical (<1ms requirement)
- Cost-sensitive batch operations
Supported Transforms
| Transform | Description | Example |
|---|---|---|
var-to-const | Modernize variable declarations | var x = 1 -> const x = 1 |
add-types | Insert TypeScript annotations | function f(x) -> function f(x: string) |
add-error-handling | Wrap in try/catch | Bare calls -> try/catch blocks |
async-await | Convert Promise chains | .then().catch() -> async/await |
extract-function | Extract code blocks | Inline code -> named function |
inline-variable | Inline single-use variables | Remove intermediate vars |
add-jsdoc | Generate documentation | Bare functions -> JSDoc comments |
Performance
- Execution: <1ms per transform
- Cost: $0 (no LLM invocation)
- Speedup: 352x compared to LLM inference
- Confidence threshold: >90% pattern match required
Agents Used
agents/coder/- Fallback for unmatched patterns
Tool Use
Invoke via babysitter process: methodologies/ruflo/ruflo-task-routing
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/ruflo/skills/agent-booster/SKILL.mdView on GitHub Overview
Agent Booster is a WASM-compiled engine that performs simple, well-defined code transforms without invoking an LLM. It bypasses LLM inference for pattern-matched transforms, delivering sub-millisecond execution at zero cost. It supports transforms such as var-to-const, add-types, add-error-handling, async-await, and more.
How This Skill Works
Agent Booster uses prebuilt WASM routines to apply strict pattern matches against code. When a transform matches, it runs instantly without LLM calls; if no pattern matches, control falls back to the fallback coder agent. A confidence threshold of over 90% is required for a transform to be applied.
When to Use It
- Simple, deterministic code transforms
- High-frequency repetitive modifications
- Latency-critical workflows requiring sub-millisecond response
- Cost-sensitive batch operations
- Transforms that fit the supported set (var-to-const, add-types, add-error-handling, async-await, extract-function, inline-variable, add-jsdoc)
Quick Start
- Step 1: Invoke via babysitter process: methodologies/ruflo/ruflo-task-routing
- Step 2: Specify the target transform from the supported list (e.g., var-to-const)
- Step 3: Review the transformed output; if no pattern matches, the system falls back to agents/coder/ for unmatched transforms
Best Practices
- Clearly define each intended transform before enabling (e.g., var-to-const, add-types).
- Keep transforms idempotent to avoid repeated changes on re-runs.
- Ensure pattern-match coverage exceeds 90% before deployment.
- Provide a clean fallback path to the coder agent for unmatched patterns.
- Validate results with quick tests or linting after transformation.
Example Use Cases
- var x = 1 -> const x = 1
- function f(x) -> function f(x: string)
- Bare calls -> try { ... } catch { ... }
- .then().catch() -> async/await
- Inline code -> named function
