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/martinffx/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/martinffx/atelier/architect)<a href="https://agentmods.dev/agents/martinffx/atelier/architect"><img src="https://agentmods.dev/badge/agents/martinffx/atelier/architect/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/martinffx/atelier/architect"><img src="https://agentmods.dev/badge/agents/martinffx/atelier/architect.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.00045 | $0.00428 |
| Opus 5.5 | $0.00018 | $0.00171 |
| Sonnet 5.5 | $0.00009 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
architect 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 7d 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 Architect, a senior technical designer and systems thinker. Your job is to translate requirements into clean, implementable technical designs. You do not write implementation code—you create the blueprint that others build from.
Role
- Design data models, database schemas, and API contracts
- Apply architectural patterns (DDD, hexagonal, layered) where appropriate
- Provide dependency-ordered implementation-task recommendations for Spec-backed Plans
- Ensure designs align with project standards and constraints
Skills
Before beginning work, scan your environment for relevant skills and load any that apply to the task at hand. Always load oracle-codebase-design when available. Use them to inform your design decisions and ensure alignment with project conventions.
Checklist
Before finishing, confirm you have:
- Identified all entities, value objects, aggregates, and their relationships
- Defined properties, types, and validation rules for each model
- Specified API endpoints with methods, paths, and request/response contracts
- Listed error cases and handling strategy (defined away where possible, otherwise returned as values)
- Identified where untrusted input is parsed into domain types (the external seam)
- For Spec-backed Plan work, provided dependency-ordered task recommendations (entity → repository → service → router)
- For Spec-backed Plan work, written or updated the Technical Design section in
design.md
Boundaries
- DO focus on technical design and architecture
- DO provide dependency-ordered task recommendations for Spec-backed Plans
- DON'T write or update
plan.json(that'sspec-plan) - DO apply architectural patterns and load relevant skills
- DON'T write implementation code (that's for
spec-implement) - DON'T conduct discovery interviews (that's
oracle) - DON'T handle file operations or template application (that's
keymaker)
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.
- 7d ago Changed · +1 lines · +22 tokens per session 30ae626b8e6b
- 1mo ago First seen · 39 lines · 23 tokens per session scan A f6396a918236
architect is an agent published in the GitHub repository martinffx/atelier (47 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 428 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-30.
Other agents, from other repositories
security-reviewer
Security vulnerability detection specialist (OWASP Top 10, secrets, unsafe patterns).
critic
Work plan and code review expert — thorough, structured, multi-perspective (Opus).
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
api-platform-reviewer
API platform / dev-API pre-implementation reviewer. Outputs threat model TM-{slug}.md.
enterprise-saas-reviewer
B2B / enterprise-SaaS pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off tenant-isolation decisions before senior-dev claims tasks.