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.
git 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/generate-plan-for-spec)<a href="https://agentmods.dev/commands/bacchus-labs/wrangler/generate-plan-for-spec"><img src="https://agentmods.dev/badge/commands/bacchus-labs/wrangler/generate-plan-for-spec.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.1 | $0.00011 | $0.00587 |
| Opus 5 | $0.00005 | $0.00293 |
| Sonnet 5 | $0.00002 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
generate-plan-for-spec 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 8d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wrangler:generate-plan-for-spec
Break a specification into discrete MCP issues in .wrangler/issues/.
Arguments
$1— spec-path: Path to spec file (e.g.,.wrangler/specifications/SPEC-000001-feature-name.md)
Instructions
- Validate the spec path exists and is markdown
- Read and parse the specification:
- Extract Implementation Plan, Goals, Acceptance Criteria
- Identify discrete work units
- For each work unit, create an MCP issue using
issues_create:- Title: Action-oriented (verb phrase)
- Description: Full implementation details with TDD steps
- Project: Set to the spec filename for linking
- Labels:
["plan-step", "implementation"]
- Ensure issues are ordered with proper dependencies
- Output summary of created issues
Issue Generation Guidelines
| Guideline | Description |
|---|---|
| Atomic | Each issue = one logical unit of work |
| Focused | Completable in one session (<250 LOC) |
| Ordered | Dependencies flow from earlier to later |
| Testable | Has verifiable acceptance criteria |
| Action-oriented | Title starts with verb (Implement, Add, Create, Fix) |
Parsing Priority
- Implementation Plan — Primary source (phases become issue groupings)
- Goals — Secondary if no Implementation Plan
- Acceptance Criteria — Mapped to issue acceptance criteria
Each Issue Must Include
Following the writing-plans skill requirements:
- Exact file paths (create/modify/test)
- Complete code examples for all 5 TDD steps
- Exact commands with expected output
- Clear acceptance criteria
- Dependencies on other tasks
Output
Created N issues from SPEC-000001-feature-name.md:
ISS-000042: Setup database schema
ISS-000043: Implement user model
ISS-000044: Add validation logic
...
Issues linked to project: SPEC-000001-feature-name.md
View status: /wrangler:issues
Relationship to write-plan
This command is a focused version of /wrangler:write-plan:
- write-plan: General planning workflow, may prompt for input
- generate-plan-for-spec: Takes a spec file directly, no prompts
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.
- 8d ago First seen · 84 lines · 11 tokens per session scan A d9e7f497c19a
generate-plan-for-spec is a command published in the GitHub repository bacchus-labs/wrangler (4 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 587 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.