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/helpgit clone --depth 1 https://github.com/bacchus-labs/wranglerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/bacchus-labs/wrangler/help)<a href="https://agentmods.dev/commands/bacchus-labs/wrangler/help"><img src="https://agentmods.dev/badge/commands/bacchus-labs/wrangler/help.svg" alt="Measured on agentmods" height="20"></a>What 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.00008 | $0.02040 |
| Opus 5 | $0.00004 | $0.01020 |
| Sonnet 5 | $0.00002 | $0.00408 |
| Haiku 4.5 | $0.00001 | $0.00204 |
Grade A, and why
help 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrangler Help
Comprehensive documentation for the Wrangler project governance plugin.
Arguments
Parse $ARGUMENTS for one optional positional argument:
$1(optional) — command-name: Show help for a specific command
| Argument | Shows |
|---|---|
| (none) | Full help documentation |
brainstorm |
Brainstorming workflow details |
write-plan |
Plan creation details |
generate-plan-for-spec |
Spec-to-issues breakdown |
implement |
Autonomous implementation |
issues |
Status display details |
Overview
Wrangler is a project governance framework and skills library for Claude Code. It provides:
- Specification documents for planning features and changes
- MCP-based issue tracking for discrete, completable tasks
- Skills library with proven workflows and patterns
- Session hooks for automatic workspace initialization
- Constitutional governance for consistent decision-making
Core Principles
- MCP tools are the source of truth — Issues and specs managed via MCP
- Skills are mandatory when available — If a skill exists, use it
- TDD is non-negotiable — Write tests first, always
- Evidence over claims — Verify before declaring success
- Files in
.wrangler/— Centralized workspace directory
Commands
/wrangler:brainstorm
Refine rough ideas into fully-formed designs using Socratic method.
Usage
/wrangler:brainstorm
/wrangler:brainstorm "I want to add user authentication"
What It Does
- Asks clarifying questions to understand requirements
- Explores alternatives and trade-offs
- Produces a validated design ready for specification
- Invokes the
brainstormingskill
/wrangler:write-plan
Create detailed implementation plans with bite-sized tasks.
Usage
/wrangler:write-plan
/wrangler:write-plan .wrangler/specifications/SPEC-000001-feature.md
What It Does
- Analyzes specification or requirements
- Breaks down into discrete MCP issues
- Each issue includes TDD steps and exact file paths
- Optionally creates architecture reference document
- Invokes the
writing-plansskill
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.
- 3d ago First seen · 356 lines · 8 tokens per session scan A 898adff0ab67
help is a command published in the GitHub repository bacchus-labs/wrangler (4 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 2,040 once invoked, about $0.0000 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.