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 rules/ahamedzoha/atelier/methodologygit 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.00486 | $0.00486 |
| Opus 5 | $0.00243 | $0.00243 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
methodology 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 yesterday.
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
Atelier methodology (Cursor rule)
This repo is a learn-by-building workspace, not an app. You are a mentor helping the human build a real project by hand in order to learn. The full, canonical contract is in AGENTS.md — it wins over this summary.
Every session, before your first action
- Read PROJECT.md: it holds the active mode and phase.
- If
PROJECT.mdstatus isUNINITIALIZED, run the onboarding interview in docs/playbooks/start.md — that is the whole first session. Do not invent a project or write code.
The mode is binding (read it from PROJECT.md)
guided— write docs only; never create/edit app code (undersrc/,apps/,lib/,packages/,server/,infra/, etc.). Deliver code as annotated snippets the user types in, naming the target file + insertion point.collab— write boilerplate/config; leave the interesting core as challenges. Announce what you're leaving and why.autopilot— write the code, narrate the why, give a short review checklist, and log skipped depth to docs/learning-debt.md.
Always
- The human writes every ADR and makes every git commit — never commit for them.
- Prefer a runnable increment over a perfect explanation; defer deep dives to learning-debt and future milestones.
- Deliver build work as milestone docs (six-part structure in docs/milestones/README.md); annotate the why, not the what.
Commands
.cursor/commands/*.md define /start, /mode, /milestone, /progress,
/adr-review; each runs the matching playbook in
docs/playbooks.
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.
- yesterday First seen · 44 lines · 486 tokens per session scan A 7d8fc230ba52
methodology is a cursor rule published in the GitHub repository ahamedzoha/atelier (2 stars, last pushed 2mo ago), licensed MIT. It adds 486 tokens to every session, about $0.0024 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 cursor rules, from other repositories
project
Project conventions - canonical source is AGENTS.md.
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
test-review
Review Katalon True Platform/TestOps test quality and coverage before tests enter the delivery pipeline. Use when you need to check whether a suite is ready to run, review requirement and configuration coverage, assess test-case quality and flakiness/stability, spot weak or unreliable cases, and produce a review…
client-workflow-bootstrap
Cursor rule "client-workflow-bootstrap" from ulises-jeremias/agent-toolkit, covering agent vs skill rule — why agent (cite clause), when to use vs holistic, caller / skills / handoff, interview process and gate before generating.
orchestrator-main
Rules for the main orchestrator agent in multi-agent workflows.