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/aadivar/shiplog/sprintgit clone --depth 1 https://github.com/aadivar/shiplogWrote 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/aadivar/shiplog/sprint)<a href="https://agentmods.dev/commands/aadivar/shiplog/sprint"><img src="https://agentmods.dev/badge/commands/aadivar/shiplog/sprint.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.1 | $0.00000 | $0.00460 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
sprint 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 6d 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
/shiplog sprint
Start a new sprint with session log archival.
Trigger
User runs /shiplog sprint <n> or /shiplog sprint
Behavior
Step 1: Validate setup
Check that .shiplog/config.json exists. If not:
"Shiplog is not initialized. Run
/shiplog initfirst."
Step 2: Determine sprint number
- If user provided a number (e.g.,
/shiplog sprint 3), use that - If no number, read
docs/PROGRESS.mdto get current sprint and increment by 1
Step 3: Archive previous sprint
Read docs/PROGRESS.md and extract the session log entries for the current sprint.
Create an archive file:
- Path:
docs/archive/sprint-{N}.md(createdocs/archive/if it doesn't exist) - Content: The session log entries from the completed sprint, with a header
Step 4: Update PROGRESS.md
Edit docs/PROGRESS.md:
- Update "Sprint" in Current State to the new sprint number
- Clear the Session Log section and add a fresh table header for the new sprint
- Update "Last Session" date
- Keep the "What's Next" section (user will update it)
Step 5: Generate sprint summary
Count from the archived sprint:
- Number of session entries
- Features completed (cross-reference with PRD.md)
- Features still in-progress
Step 6: Confirm and ask for focus
Sprint {N} started!
Sprint {N-1} summary:
Sessions: {count}
Features completed: {count}
Features in-progress: {count}
Archived to: docs/archive/sprint-{N-1}.md
What's the focus for Sprint {N}?
Use AskUserQuestion to ask for the sprint focus, then update the "Focus" field in PROGRESS.md's Current State.
Rules
- Always archive before clearing — never lose session history
- Sprint numbers must be positive integers
- Don't allow going backwards (sprint 2 after sprint 3)
- Create docs/archive/ directory if it doesn't exist
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.
- 6d ago First seen · 59 lines · 0 tokens per session scan A 651c15fe5d2a
sprint is a command published in the GitHub repository aadivar/shiplog (3 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 460 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
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
sm-sail
Command "sm-sail" from ScienceIsNeato/slop-mop, covering /sm-sail — drive a pr to green, autonomously, the loop, when sail parks on review threads, when to stop before "pr ready" — only two reasons and expect convergence, not one pass.
sm-buff
You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…
sm-wake-angry-drunk-captain
The last-resort verb. Use it ONLY when the loop is genuinely exhausted: barnacles filed, gates green or truly unfixable, and the single remaining move is a human judgment call no sm verb can make for you.
sm-barnacle
Use when sm itself gives invalid guidance, blocks valid work, produces confusing output, or breaks install/upgrade/refit flow. Do not use this for real target-repo failures; fix those through the normal rail.
sm-init
Run when you find a repo with sm installed but no .sbconfig.json — or after upgrading slopmop to pick up new gates.