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 instructions/ahamedzoha/atelier/claude-mdgit 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/instructions/ahamedzoha/atelier/claude-md)<a href="https://agentmods.dev/instructions/ahamedzoha/atelier/claude-md"><img src="https://agentmods.dev/badge/instructions/ahamedzoha/atelier/claude-md.svg" alt="Measured on agentmods" 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.00374 | $0.00374 |
| Opus 5 | $0.00187 | $0.00187 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
atelier CLAUDE.md 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 5d 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
CLAUDE.md
This project's full AI contract lives in AGENTS.md — read it
in full. It is canonical; this file only adds Claude Code specifics.
@AGENTS.md
First thing, every session
- Read
PROJECT.md. - If its status is
UNINITIALIZED, run thestartskill (the onboarding interview) before anything else. - Otherwise, note the active mode and current phase and proceed within the mode's rules.
Skills available in this repo
Invoke with /<name>; each skill just runs the matching playbook in
docs/playbooks/, so behavior stays consistent across tools.
/start— onboarding interview: turn this template into your project./mode— switch betweenguided,collab, andautopilot./milestone— produce the next guided milestone build doc./progress— compare repo state to the roadmap, log progress, plan next session./adr-review— review an ADR you've written (never write one for you)./lesson— produce or continue a deep-dive learning-track lesson.
Memory
If you keep cross-session memory, record: the user's background and goals (from
onboarding), the active mode, and where the current phase stands. Re-read
PROJECT.md each session rather than trusting stale memory — it is the live
state.
Mode reminder
The mode in PROJECT.md is binding. In guided mode you must never create
or edit application code — deliver it as an annotated snippet for the user to
type. See AGENTS.md §2.
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.
- 5d ago First seen · 40 lines · 374 tokens per session scan A b3ab5f50e686
atelier CLAUDE.md is an instructions file published in the GitHub repository ahamedzoha/atelier (2 stars, last pushed 2mo ago), licensed MIT. It adds 374 tokens to every session, about $0.0019 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 instructions, from other repositories
trellis AGENTS.md
Instructions for craigcossairt/trellis, covering agents.md , project, what i need from agents, current state - source of truth pointers and tech stack.
trellis CLAUDE.md
Instructions for craigcossairt/trellis, a project described as: The structure a project grows on: a free starter template for AI-assisted development. One AGENTS.md every tool reads (Claude Code, Cursor, Grok Build, Codex, Gemini CLI, Copilot), TDD + bug-fix methodology, secret guardrails, optional local knowledge…
trellis copilot-instructions.md
Instructions for craigcossairt/trellis: Read and follow AGENTS.md at the repository root - it is the canonical instruction file for all AI agents on this project. Full methodology docs live in docs/methodology/: TDD workflow, bug-fix protocol, and session habits. Append bug patterns to docs/common-gotchas.md and…
trellis GEMINI.md
Instructions for craigcossairt/trellis: Read and follow AGENTS.md in this directory - it is the canonical instruction file for all AI agents on this project. Full methodology docs live in docs/methodology/.
sdd-starter CLAUDE.md
Claude Code instructions for KazukiShinomiya/sdd-starter, covering claude.md, 共有文脈（全エージェント共通）, このプロジェクトの核（変更時に守る） and claude 固有の運用指針.
sdd-starter AGENTS.md
AGENTS.md instructions for KazukiShinomiya/sdd-starter, covering agents.md - project context (shared memory for ai agents), active tech stack, recent changes and 憲法の扱い（テンプレ本体の開発）.