Borrowing it
Nothing to install: this file belongs to richardthe3rd/cambridge-beer-festival-app. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/richardthe3rd/cambridge-beer-festival-app/main/.claude/commands/plan-issues.mdgit clone --depth 1 https://github.com/richardthe3rd/cambridge-beer-festival-appWrote 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/richardthe3rd/cambridge-beer-festival-app/plan-issues)<a href="https://agentmods.dev/commands/richardthe3rd/cambridge-beer-festival-app/plan-issues"><img src="https://agentmods.dev/badge/commands/richardthe3rd/cambridge-beer-festival-app/plan-issues/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/richardthe3rd/cambridge-beer-festival-app/plan-issues"><img src="https://agentmods.dev/badge/commands/richardthe3rd/cambridge-beer-festival-app/plan-issues.svg" alt="Reviewed on agentmods" width="80" 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.00419 |
| Opus 5 | $0.00005 | $0.00210 |
| Sonnet 5 | $0.00002 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
plan-issues 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 11d 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
Plan Issues
Spawn parallel planning agents for one or more GitHub issue numbers.
Usage: /plan-issues #270 #324 or /plan-issues 270 324 355
For each issue number provided:
- Read the issue from GitHub:
mcp__github__issue_read(method:get) for the title and body, then (method:get_comments) for any triage comments —getalone does not return comments. - Explore the affected files to understand the current code.
- Produce a plan in the exact contract format below.
Spawn all planning agents in parallel (one per issue, subagent_type: claude). Use model: haiku for single-file mechanical fixes; model: sonnet for multi-file or architectural changes. Each agent receives: the issue body, relevant file excerpts, and the planning contract below.
Planning Agent Contract
Every plan must output exactly these three sections — implementation agents receive them verbatim:
### Allowed files (HARD CONSTRAINT)
- lib/path/to/file.dart
- test/path/to/file_test.dart
# Nothing outside this list may be touched.
### Model recommendation
haiku / sonnet — one-line rationale
### Phase N — <short name>
Files: (subset of allowed list)
Changes: (exact description — line numbers where possible)
Verification: (command to run)
Done signal: (what "done" looks like)
Model selection guide
See the model selection table in AGENTS.md ("Parallel Work with Subagents → Model Selection"). In short: haiku for single-file mechanical changes and pattern-following tests; sonnet for multi-file or architectural changes, nullable/sentinel patterns, and type-system work.
After all planning agents complete, present the plans to the user for approval before any implementation begins.
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.
- 11d ago First seen · 51 lines · 11 tokens per session scan A 03732105021c
plan-issues is a command published in the GitHub repository richardthe3rd/cambridge-beer-festival-app (2 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 419 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.