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/backloggit clone --depth 1 https://github.com/ds1/boilerplate.mdWhat 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.00222 |
| Opus 5 | $0.00000 | $0.00111 |
| Sonnet 5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
backlog 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 2d 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 Backlog
Review the project backlog and upcoming work.
Steps
-
Check for backlog in this priority order:
_planning/backlog.md_planning/sprint.mdSTATUS.md(the "Up Next" section)- GitHub Issues (run
gh issue list --limit 20if the above don't exist)
-
Present the backlog organized by priority:
- Current Sprint — what's committed for this cycle
- High Priority — should be done soon
- Medium Priority — planned but not urgent
- Low Priority / Ideas — nice to have
-
If the user asks to reprioritize, update the source file accordingly.
-
If no backlog exists anywhere, offer to create
_planning/backlog.mdfrom the user's input or by scanning STATUS.md and GitHub Issues.
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.
- 2d ago First seen · 26 lines · 0 tokens per session scan A 10e03e6cb8e7
backlog 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 222 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
tickets
Command "tickets" from chohra-med/expo_boilerplate, covering invocation, source a — a ticket mcp (linear / github issues / jira / …), source b — an inline plan (no ticket system), then: build and hard rules.
board-csk
Team board — see who holds which item, claim one, hand it over, complete it.
fix-issue
이슈 #$ARGUMENTS 를 처리한다(이슈 우선 워크플로).
jira-instance-migration
Repoint Jira configuration and regenerate catalogs after explicit approval.
jira-components
Plan and reconcile Jira Components after explicit approval.
next-sprint-design
You are helping a DevOps engineer prepare a sprint kickoff message for Slack.