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/chrisdev1187/claude-code-forge/sprint-endgit clone --depth 1 https://github.com/chrisdev1187/claude-code-forgeWhat 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.00323 |
| Opus 5 | $0.00000 | $0.00161 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
sprint-end 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 yesterday.
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
/sprint-end — Close Current Sprint
Run this when all sprint goals are complete and verified.
Steps
-
Verify all sprint goals are met:
- Re-read
docs/sprints/sprint-N-gate.mdD1 "Done means" criteria - Confirm each criterion is testably true
- Confirm git tag
verified-[component]exists for each delivered component
- Re-read
-
Update
docs/MASTER_STATE.md:- Mark sprint as complete
- Update all component statuses to final state
- Fill in LAST VERIFIED TAG section
-
Commit the sprint close:
rtk git add docs/MASTER_STATE.md docs/SESSION_LOG.md rtk git commit -m "chore: close sprint N — [brief summary of what shipped]" rtk git tag "sprint-N-complete" -
Merge to dev/main:
rtk git checkout dev rtk git merge session/YYYY-MM-DD --no-ff -m "merge: sprint N complete" rtk git push origin dev -
Update
docs/sprints/CURRENT_SPRINT.mdto N+1 (ready for /new-sprint)
Before closing: checklist
- All D1 "Done means" criteria checked
- All components have verified-* git tags
- MASTER_STATE.md updated
- SESSION_LOG.md has end-of-sprint entry
- No hardcoded credentials in any committed file
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.
- yesterday First seen · 40 lines · 0 tokens per session scan A 4454e01acfc8
sprint-end is a command published in the GitHub repository chrisdev1187/claude-code-forge (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 323 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
advisor
Advisory gate for triage or plan decisions. Spawns a second-opinion agent that challenges assumptions, surfaces risks, and proposes alternatives before the decision commits. Based on Anthropic advisor tool pattern.
guide
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.
pm-review
Review local git diff with reasoning + snippets; cross-check; dispose findings into the rules library.
new
Creates a new item in a module that supports the new capability.
card
Open one self-contained OverClick card.
linear-bulk
Apply the same change to many Linear issues at once. Dry-run by default.