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/ahamedzoha/atelier/milestonegit clone --depth 1 https://github.com/ahamedzoha/atelierWrote 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/ahamedzoha/atelier/milestone)<a href="https://agentmods.dev/commands/ahamedzoha/atelier/milestone"><img src="https://agentmods.dev/badge/commands/ahamedzoha/atelier/milestone.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.00122 |
| Opus 5 | $0.00000 | $0.00061 |
| Sonnet 5 | $0.00000 | $0.00024 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
milestone 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
/milestone — next build guide
Produce the next build doc. Run the workflow in
docs/playbooks/milestone.md: read the active
mode and current phase from PROJECT.md, find the next milestone in
docs/progress.md, and write docs/milestones/<phase>.<n>-<slug>.md in the
six-part format (Concept · ADR · Guided build · Challenges · Verify · Stretch).
Respect the mode — in guided, deliver annotated snippets only and never edit
app code.
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 · 10 lines · 0 tokens per session scan A d3860fc9a8eb
milestone is a command published in the GitHub repository ahamedzoha/atelier (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 122 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
worktree
Set up parallel agent sessions on independent tasks via git worktrees. Use when asked to '/worktree', 'git worktree', 'parallel branches', 'isolated branch workspace', 'work on two things at once'.
bug-report
Structured bug-fix protocol per docs/methodology/bug-protocol.md. Use when asked to '/bug-report', 'I found a bug', 'something is broken', 'fix this bug', 'report a bug', 'this is broken'.
tdd
TDD workflow - red-green-refactor per docs/methodology/tdd.md. Use when asked to '/tdd', 'TDD workflow', 'red-green-refactor', 'test-first development', 'write the failing test first'.
checklist
成果物（spec/plan/tasks）の内部品質を観点チェックリストで検査する.
taskstoissues
tasks.md を課題トラッカー用の issue ドラフトに変換する（既定はゼロ依存の Markdown 出力）.
amend
既存の spec を改訂し、変更履歴と下流（plan/tasks）への波及を記録する.