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/progressgit clone --depth 1 https://github.com/ahamedzoha/atelierWhat 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.00113 |
| Opus 5 | $0.00000 | $0.00056 |
| Sonnet 5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
progress 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
/progress — where am I, what's next
Run the workflow in docs/playbooks/progress.md:
read PROJECT.md, docs/progress.md, and the actual repo (trust the repo over
the doc). Locate me, name concrete progress, append a dated session-log entry,
propose the single next action, and check docs/learning-debt.md for anything
worth pulling in. If I seem stuck, shrink the next step — don't answer with more
theory.
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 · 9 lines · 0 tokens per session scan A 10b5b4622f9d
progress 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 113 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
optimize
Command "optimize" from doccker/cc-use-exp, covering 第 0 步：范围选择, 统计文件数和行数, 第 1 步：项目画像, 扫描内容 and 输出格式.
review
Command "review" from doccker/cc-use-exp, covering 参数解析, 解析参数, 提取模式和目标, 如果指定了 commit，验证其有效性 and 模式 1：full（默认）.
project-scan
扫描项目生成配置（CLAUDE.md/restart.sh/ignore/Docker）.
design
技术设计（doc 文档框架 / checklist 质量检查）.
requirement
需求分析（doc 文档框架 / interrogate 极刑审问）.
commit-msg
Command "commit-msg" from doccker/cc-use-exp, covering 生成 git commit message, 执行步骤, 1. 获取变更内容, 查看已暂存的变更 and 如果没有暂存内容，查看所有变更.