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 skills/ahamedzoha/atelier/milestonenpx skills add ahamedzoha/atelier --skill 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/skills/ahamedzoha/atelier/milestone)<a href="https://agentmods.dev/skills/ahamedzoha/atelier/milestone"><img src="https://agentmods.dev/badge/skills/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.1 | $0.00047 | $0.00145 |
| Opus 5 | $0.00023 | $0.00072 |
| Sonnet 5 | $0.00009 | $0.00029 |
| Haiku 4.5 | $0.00005 | $0.00015 |
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 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
Run the workflow in docs/playbooks/milestone.md.
Read the active mode and current phase from PROJECT.md first, find the next
milestone in docs/progress.md, then write
docs/milestones/<phase>.<n>-<slug>.md from the six-part template. Respect the
mode (in guided, deliver annotated snippets only — 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.
- 5d ago First seen · 12 lines · 47 tokens per session scan A 9eda9be00972
milestone is a skill published in the GitHub repository ahamedzoha/atelier (2 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 145 once invoked, about $0.0002 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 skills, from other repositories
daily-brief
Start-of-day ranked brief - open issues, recent commits, work in progress, and anything waiting on a human decision. Use when asked for a 'daily brief', 'morning brief', 'what should I work on today', 'start my day', 'catch me up'.
launch-check
Run a pre-demo/pre-launch audit of the app - test data, broken screens, missing error states, brand consistency. Use when asked to 'demo check', 'launch check', 'pre-demo audit', 'check before user interview', 'audit before demo'.
review-dependency-updates
Review outdated dependencies, security-scan each candidate bump against OSV.dev, then apply only the safe updates and PR them. Use when asked to 'review dependency updates', 'what can/should be updated', 'are we exposed to ', 'bump dependencies safely'.
fable-skill
Fable-class agentic operating discipline, gated to task risk and domain so overhead scales with stakes. Trigger on: explicit /fable-skill or $fable-skill; debugging or diagnosing a failure; changes spanning multiple files; refactors and migrations; irreversible or destructive actions; ambiguous goals needing…
learn
Review the current conversation and update project knowledge artifacts - common-gotchas.md (bug patterns), AGENTS.md (conventions), agent memory (cross-session). Use when asked to '/learn', 'what did we learn', 'capture lessons', 'update common-gotchas'.
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'.