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/progressnpx skills add ahamedzoha/atelier --skill 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.00051 | $0.00163 |
| Opus 5 | $0.00026 | $0.00081 |
| Sonnet 5 | $0.00010 | $0.00033 |
| Haiku 4.5 | $0.00005 | $0.00016 |
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 2d 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/progress.md.
Read PROJECT.md, docs/progress.md, and the actual repo (trust the repo over
the doc). Locate the user, name concrete progress, append a dated session-log
entry, propose the single next action, and glance at docs/learning-debt.md for
anything worth pulling in. If the user is demotivated, shrink the next step —
never answer a stuck user 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.
- 2d ago First seen · 13 lines · 51 tokens per session scan A 84644d4c0921
progress is a skill published in the GitHub repository ahamedzoha/atelier (2 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 163 once invoked, about $0.0003 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
java-dev
Java 开发规范，包含命名约定、异常处理、Spring Boot 最佳实践等.
query-performance-safety
当代码涉及循环内查询、批量 ID 查询、IN 子句、BFS/递归遍历、嵌套 service 调用时触发。防止 N+1 查询、IN 子句过长、递归内存炸裂等性能陷阱。.
refactor-safety
当用户要求重构代码（提取组件、合并重复逻辑、重命名变量、优化结构）时触发。提供重构安全检查清单，防止丢失原始上下文。.
cc-java-dev
Java 开发规范，包含命名约定、异常处理、Spring Boot 最佳实践等.
api-design-safety
当设计或修改 REST API 响应结构、处理 API 返回值，或生成 Excel/CSV/PDF/对账文件等下游产物时触发。防止 API 设计缺陷导致的字段错位、类型歧义，以及生成产物时关键字段缺失但静默成功的问题。.
frontend-dev
前端开发规范，包含 Vue 3 编码规范、UI 风格约束、TypeScript 规范等.