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/ds1/boilerplate.md/statusgit clone --depth 1 https://github.com/ds1/boilerplate.mdWrote 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/ds1/boilerplate.md/status)<a href="https://agentmods.dev/commands/ds1/boilerplate.md/status"><img src="https://agentmods.dev/badge/commands/ds1/boilerplate.md/status.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.00000 | $0.00179 |
| Opus 5 | $0.00000 | $0.00089 |
| Sonnet 5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
status 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.
What it actually says
Review Project Status
Read the current project state and summarize it concisely.
- Read
STATUS.mdin the project root. If it doesn't exist, say so and offer to create one. - Optionally scan recent git log (last 5 commits) for additional context.
- Present a summary:
- In Progress — what's actively being worked on
- Blockers — anything stuck or waiting on input
- Up Next — what's queued after current work
- Recent Completions — last few finished items
Keep the summary short and actionable. Don't read CLAUDE.md for status. That's not where it lives.
By @ds1 — boilerplate.md
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 · 18 lines · 0 tokens per session scan A 58b9cf19711f
status is a command published in the GitHub repository ds1/boilerplate.md (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 179 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-08-31.
Other commands, from other repositories
create-pr
Create a pull request following the official template.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
audit
Command "audit" from chohra-med/expo_boilerplate, covering invocation, checks and output.
build
Command "build" from chohra-med/expo_boilerplate, covering command: build — run the sdd pipeline over tasks.md, invocation, per-task cycle, gates (constitution) and output.
board-csk
Team board — see who holds which item, claim one, hand it over, complete it.