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/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/plan)<a href="https://agentmods.dev/commands/xrensiu/claude-code-forge/plan"><img src="https://agentmods.dev/badge/commands/xrensiu/claude-code-forge/plan/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/xrensiu/claude-code-forge/plan"><img src="https://agentmods.dev/badge/commands/xrensiu/claude-code-forge/plan.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.00000 | $0.00705 |
| Opus 5.5 | $0.00000 | $0.00282 |
| Sonnet 5.5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
plan 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 1mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/plan Command
Create a detailed implementation plan from a PRD or design document.
Usage
/plan <prd-path> [options]
Examples
# Basic usage - create plan from PRD
/plan docs/prd/user-auth.md
# With design document
/plan docs/prd/user-auth.md --design docs/adr/001-auth-architecture.md
# Specify output format
/plan docs/prd/user-auth.md --format json
# Limit scope
/plan docs/prd/user-auth.md --scope "login and registration only"
# Quick plan for small feature
/plan --quick "Add password reset functionality"
Options
| Option | Description | Default |
|---|---|---|
--design <path> |
Path to architecture/design document | None |
--format <md|json> |
Output format | md |
--scope <description> |
Limit planning scope | Full PRD |
--output <path> |
Custom output path | docs/plans/YYYY-MM-DD-<name>.md |
--quick <description> |
Quick plan without PRD | N/A |
--no-code |
Generate task list without full code | false |
What It Does
- Reads the PRD (and design doc if provided)
- Activates the
writing-plansskill - Dispatches the
planneragent - Generates a detailed implementation plan
- Saves to
docs/plans/ - Asks which execution mode to use
Output
The command produces:
-
Plan Document:
docs/plans/YYYY-MM-DD-<feature-name>.md- Task breakdown with complete code
- Dependency graph
- Verification commands
- Time estimates
-
Optional JSON:
docs/plans/YYYY-MM-DD-<feature-name>.json- Machine-readable format for automation
After Planning
The command will ask:
Plan created with 12 tasks (~35 min estimated).
How would you like to execute?
A) Subagent-Driven Development
- Each task by fresh subagent
- Two-stage review (spec + quality)
- Best for: Production code, complex features
B) Executing-Plans
- Batch execution with checkpoints
- Review at milestones
- Best for: MVPs, rapid iteration
C) Manual
- I'll execute tasks myself
- Just save the plan
Choice [A/B/C]:
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.
- 1mo ago First seen · 111 lines · 0 tokens per session scan A a0b5cf15a9bb
plan is a command published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 705 tokens. 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-09-05.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
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.