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 skills add ahamedzoha/atelier --skill progressgit 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/progress)<a href="https://agentmods.dev/skills/ahamedzoha/atelier/progress"><img src="https://agentmods.dev/badge/skills/ahamedzoha/atelier/progress/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ahamedzoha/atelier/progress"><img src="https://agentmods.dev/badge/skills/ahamedzoha/atelier/progress.svg" alt="Reviewed on agentmods" width="80" 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.00051 | $0.00163 |
| Opus 5.5 | $0.00020 | $0.00065 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 13 lines · 51 tokens per session scan A 84644d4c0921
progress is a skill published in the GitHub repository ahamedzoha/atelier (3 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 163 once invoked, about $0.0002 per session on Opus 5.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
setup
Walk a new project through setting up this template - interview the owner, fill in the context files, wire the safety rails, and verify it worked. Use when asked to "set up trellis", "set up this template", "walk me through SETUP.md", "help me get started", "configure this project", "initialise the template".
trellis-survey
Check this template's static wiring and setup - missing hooks, unreachable skills, unfinished context files. Runtime activation and trust require separate checks. Read-only. Use when asked "what do I have", "is everything set up", "what is actually running", "audit my setup", "did I break anything", "what did I…
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'.
write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then submit to the issue tracker. Use when asked to 'write a PRD', 'create a product requirements document', 'plan a new feature'.
prd-to-issues
Break a PRD into independently-grabbable tracker issues using tracer-bullet vertical slices. Use when asked to 'PRD to issues', 'break this PRD into tickets', 'create implementation tickets from a PRD', 'turn PRD into issues'.
spec-kitty-implement-review
Orchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state transitions, rejection cycles, arbiter escalation, and dependency-aware sequencing across all 13 supported coding agents. Triggers: "implement and review WPs", "run the implement-review loop"…