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.
git clone --depth 1 https://github.com/tunahanaliozturk/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/tunahanaliozturk/atelier/status)<a href="https://agentmods.dev/commands/tunahanaliozturk/atelier/status"><img src="https://agentmods.dev/badge/commands/tunahanaliozturk/atelier/status/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/commands/tunahanaliozturk/atelier/status"><img src="https://agentmods.dev/badge/commands/tunahanaliozturk/atelier/status.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.00021 | $0.00233 |
| Opus 5 | $0.00010 | $0.00117 |
| Sonnet 5 | $0.00004 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
status 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 10d 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
Read the most recently modified mission file under .atelier/missions/ and parse it with
parseMission (lib/mission.mjs). If there is no mission file, say there is no active
mission and stop.
Render, in this order:
- The goal.
- A progress line from
missionProgress+progressBar(lib/board.mjs), for example[#####-----] 50% (3/6). - The tasks grouped by status — in-progress, pending, blocked, done — each a short list of ID, description, and agent.
- "Ready now": the
readyTasks(lib/schedule.mjs) output (ID, description, agent); if empty, say why (all done, all blocked, or waiting on deps). - A dependency graph from
missionMermaid(lib/board.mjs) inside a ```mermaid block. - The most recent decision-log entries.
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.
- 10d ago First seen · 20 lines · 21 tokens per session scan A 6b6f2affb0f9
status is a command published in the GitHub repository tunahanaliozturk/atelier (1 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 233 once invoked, about $0.0001 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 commands, from other repositories
heartbeat
Run a WoterClip heartbeat cycle (pick up issues, do work, report).
woterclip-status
Show WoterClip status (queue, blocked issues, last heartbeat).
docs
Docs-only change for a ready-for-agent ticket. No application code.
lead
Tech lead: classify, quiz, ticket on the owning repo, dispatch. Do not implement.
decree
Issue a decree. Seats the organization on first use, then dispatches the teams.
bob-work
Drain the board as a worker — claim pending tasks Claude can do, execute them, submit results.