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/loschenbd/claude-agent-boilerplateWrote 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/loschenbd/claude-agent-boilerplate/complete-plan)<a href="https://agentmods.dev/commands/loschenbd/claude-agent-boilerplate/complete-plan"><img src="https://agentmods.dev/badge/commands/loschenbd/claude-agent-boilerplate/complete-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/loschenbd/claude-agent-boilerplate/complete-plan"><img src="https://agentmods.dev/badge/commands/loschenbd/claude-agent-boilerplate/complete-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.00493 |
| Opus 5 | $0.00000 | $0.00246 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
complete-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 5d 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
Mark the current plan as complete and archive it.
Instructions
You are called when a plan in plans/<task-slug>/ is finished and ready to be archived.
-
Identify the plan slug. Either from the user's argument, or by scanning
plans/for the most recently modifiedplan.mdthat isn't already in_done/. -
Confirm completion. Read
plan.mdand check that all task checkboxes are marked[x]. If any are unchecked, refuse and tell the user which tasks are still open. Do not proceed. -
Update
plan.md: change the status line to**Status:** completed. -
Write
plans/<task-slug>/wrapup.mdwith:# Wrap-up: <task name> **Completed:** <date> ## What was built - <bullet list of completed tasks, with file references where relevant> ## What was deferred - <anything in the original plan or design that did not ship — and why> ## Follow-ups - <new issues this work surfaced — for future plans> ## Final state - **Files changed:** <list> - **Branch / commits:** <if applicable> -
Archive the directory: move
plans/<task-slug>/toplans/_done/<task-slug>/(create_done/if it doesn't exist). This preserves history without cluttering the active plans list. -
Tell the user: "Plan archived to
plans/_done/<task-slug>/. Wrap-up atplans/_done/<task-slug>/wrapup.md."
Rules
- Don't archive incomplete plans. If tasks are unchecked, refuse and report.
- Don't lose history. Move the directory, don't delete it. Old plans become reference material.
- Don't skip the wrap-up. A completed plan with no wrap-up is incomplete from a knowledge-management standpoint.
- If
wrapup.mdalready exists, the plan was already completed — confirm with the user before overwriting.
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.
- 5d ago First seen · 41 lines · 0 tokens per session scan A dce8ec6b2bb1
complete-plan is a command published in the GitHub repository loschenbd/claude-agent-boilerplate (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 493 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-04.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.