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/sashamitrovich/milepost/statusgit clone --depth 1 https://github.com/sashamitrovich/milepostWrote 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/sashamitrovich/milepost/status)<a href="https://agentmods.dev/commands/sashamitrovich/milepost/status"><img src="https://agentmods.dev/badge/commands/sashamitrovich/milepost/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.00011 | $0.00210 |
| Opus 5 | $0.00005 | $0.00105 |
| Sonnet 5 | $0.00002 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
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 5d 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
Milepost status
- Determine
<project-slug>(stated in the milepost SessionStart context; else: git repo root of the cwd — or the cwd itself — lowercased, non-alphanumeric runs →-, trimmed) and locate~/.claude/memory/milepost/<project-slug>/STATUS.md. - If it exists, read and display its current contents.
- Then, reflecting on the current session, update
STATUS.mdso it accurately captures: the current goal, where things stand right now, the immediate next step, and any open questions. Keep it short and present-tense (a living snapshot, not a history — that's whatlog.mdis for). - If no milepost exists yet for this project, say so and offer to start one with
/milepost.
If the user supplied text after the command, treat it as an update to fold into the status.
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.
- 5d ago First seen · 13 lines · 11 tokens per session scan A 236663785709
status is a command published in the GitHub repository sashamitrovich/milepost (6 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 210 once invoked, about $0.0001 per session on Opus 5. 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
deja
Search this machine's past AI coding sessions (deja-vu).
harness
Take one harness from "wired" to "the agent is visibly smarter for it".
goal
Complete reference for all goal-related commands — definition, refinement, execution, review, codification, and management.
relations
Complete reference for managing relationships between entities in the knowledge graph.
decisions
Complete reference for managing architectural decision records (ADRs).
guidelines
Complete reference for managing execution guidelines — testing, coding style, process, and more.