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/update-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/update-status)<a href="https://agentmods.dev/commands/ds1/boilerplate.md/update-status"><img src="https://agentmods.dev/badge/commands/ds1/boilerplate.md/update-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.00248 |
| Opus 5 | $0.00000 | $0.00124 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
update-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 4d 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
Update Project Status
Update STATUS.md to reflect current project state. The user may provide specific updates, or you may infer from recent work.
Steps
- Read the current
STATUS.md. If it doesn't exist, create one with this template:
# Project Status
Last updated: YYYY-MM-DD HH:MM
## In Progress
- [ ] Item description
## Blockers
_None_
## Up Next
- [ ] Item description
## Recently Completed
- [x] Item description (YYYY-MM-DD HH:MM)
- Apply the user's updates:
- Move completed items from "In Progress" to "Recently Completed" with date and time (YYYY-MM-DD HH:MM)
- Add new items to the appropriate section
- Update the "Last updated" timestamp with date and time
- Keep "Recently Completed" trimmed to the last 10 items. Older ones belong in CHANGELOG.md
Do NOT put any of this information in CLAUDE.md.
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.
- 4d ago First seen · 38 lines · 0 tokens per session scan A 0e5de6946bce
update-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 248 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
fix-issue
이슈 #$ARGUMENTS 를 처리한다(이슈 우선 워크플로).
next-sprint-design
You are helping a DevOps engineer prepare a sprint kickoff message for Slack.
next-issue
Fetch the next ready-for-agent issue by priority.
monitor
Monitor repository health, track issues, and identify maintenance tasks.
content-calendar
Content calendar management - scheduling and tracking content production.
project-recap
Generate a visual project recap for context switching.