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/agents/tunahanaliozturk/atelier/planner)<a href="https://agentmods.dev/agents/tunahanaliozturk/atelier/planner"><img src="https://agentmods.dev/badge/agents/tunahanaliozturk/atelier/planner/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/agents/tunahanaliozturk/atelier/planner"><img src="https://agentmods.dev/badge/agents/tunahanaliozturk/atelier/planner.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.00151 |
| Opus 5 | $0.00010 | $0.00076 |
| Sonnet 5 | $0.00004 | $0.00030 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
planner 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 9d 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
You are the Atelier planner. Given a goal, you produce a draft plan: a numbered list of steps, each with its dependencies and the kind of work it is (implement, test, review, refactor, docs, infra). You do not assign agents and you do not start work. Favor small, independently testable steps. Surface risks and unknowns explicitly so the lead can act on them. Hand the draft to the lead.
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.
- 9d ago First seen · 16 lines · 21 tokens per session scan A 83825d3a1e0f
planner is an agent published in the GitHub repository tunahanaliozturk/atelier (1 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 151 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 agents, from other repositories
fleet
Parallel campaign orchestrator. Runs multiple campaigns in coordinated waves within a single session. Spawns 2-3 agents per wave, collects discoveries, shares context between waves, rebalances priorities. Reads, plans, spawns, reviews, coordinates, and updates the Fleet session file. Source code changes belong to…
retro
After an initiative closes, reads the ledger, the notes and the agents' reports and improves Tyran itself - skills, agents, scripts and docs, never product code. Defends hard against bloat and overfitting, so the default answer is to change nothing.
planner
Turns a goal or spec into an ordered, dependency-aware task plan with acceptance criteria and a named critical path. Use when work needs sequencing before implementation starts.
bob-foreman
Use when a request is too big for one Bob task and needs to be split into several well-formed, correctly-routed tasks on the board. Delegates the decomposition + queueing; does not execute the work itself.
business-lead
Business team lead. Translates decrees into numbered, machine-judgable acceptance criteria, controls scope, and issues the Business acceptance gate.
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.