Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/bacchus-labs/wrangler/implementgit clone --depth 1 https://github.com/bacchus-labs/wranglerWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00026 | $0.00269 |
| Opus 5 | $0.00013 | $0.00134 |
| Sonnet 5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
wrangler:implement scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Parse User Input
Extract scope from user message:
- Specification reference (spec-*.md, SPEC-XXXXXX) -> use implementing-specs skill
- Single issue reference (#N, issue N, ISS-XXXXXX) -> use implementing-issue skill
- No clear scope -> ask user to specify
Skill Selection
| User Request | Skill to Use |
|---|---|
| "implement this spec" | implementing-specs |
| "implement spec-foo.md" | implementing-specs |
| "implement this spec and create PR" | implementing-specs |
| "implement issue #42" | implementing-issue |
| "implement ISS-000042" | implementing-issue |
For Specification Implementation
Use the Skill tool to load implementing-specs:
Skill: implementing-specs
The implementing-specs skill handles the full workflow: planning, execution, verification, and PR creation.
For Single Issue Implementation
Use the Skill tool to load implementing-issue:
Skill: implementing-issue
The implementing-issue skill handles TDD implementation, code review, and fix loops for a single issue.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 40 lines · 26 tokens per session scan A a92a05ef31f6
wrangler:implement is a command published in the GitHub repository bacchus-labs/wrangler (4 stars, last pushed 6mo ago), licensed MIT. It adds 26 tokens to every session and 269 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
claude-flow-swarm
Coordinate multi-agent swarms for complex tasks.
bootstrap
PACT session-start ritual — identify the session team (platform-provisioned), secretary spawn, paused-state surface, bootstrap marker.
ox-session-review
Command "ox-session-review" from sageox/ox, covering failure-mode watch-list (read first), from the ledger root. should print 0, phase 1 — scan & score (read-only), quality buckets (first match wins) and removal candidates.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
handoff
Package current state for the next agent.
xdo
Direct development by the Main Agent.