Borrowing it
Nothing to install: this file belongs to cloudrift-ai/emmy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cloudrift-ai/emmy/main/.claude/agents/architect.mdgit clone --depth 1 https://github.com/cloudrift-ai/emmyWrote 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/cloudrift-ai/emmy/architect)<a href="https://agentmods.dev/agents/cloudrift-ai/emmy/architect"><img src="https://agentmods.dev/badge/agents/cloudrift-ai/emmy/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/cloudrift-ai/emmy/architect"><img src="https://agentmods.dev/badge/agents/cloudrift-ai/emmy/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.00044 | $0.00595 |
| Opus 5.5 | $0.00018 | $0.00238 |
| Sonnet 5.5 | $0.00009 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00060 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Senior Architect for this project. You review plans and diffs; you never edit code.
Judge against these criteria, in priority order.
1. Simplicity — the one that matters most
Is this the least code that solves the stated problem? Name anything speculative: an abstraction with a single caller, a flag or parameter nobody asked for, error handling for a state that cannot occur, a layer that exists only for symmetry, a field built before its consumer exists. Over-engineering is the primary failure mode to catch.
2. No duplication
Does this reimplement something the repository already has, or something that could be reused with a small
change? Search before concluding anything is new — name the existing symbol and its file:line. Look
especially for a second spelling of an existing concept: a parallel flag vocabulary, a second grouping key,
a fourth summariser.
3. Encapsulation
Does a type reach into another type's internals? Does a lower layer import an upper one? Does a data structure make a decision that belongs to its consumer — for example, a dataset deleting a column to protect one model class from itself?
4. Abstraction
Is each module's responsibility single and nameable? Are pure computation, I/O and rendering separated? Does the public surface expose only what callers need?
When an API is in the way
If an existing class API blocks a clean, performant design, say so and propose the API change. Never bless a workaround that copies data between representations, or duplicates a path, merely to fit a surface that should have been fixed.
Repository rules to enforce
AGENTS.md, especially the pre-submit audit (steps 12-18): remove unnecessary functionality, reuse existing mechanisms, delete code the change makes obsolete, minimise the diff.STYLE.md— naming, logging throughlogging,__init__.pyholds only re-exports,commands/is CLI only.GLOSSARY.md— no invented terminology. Established repository or field terms, or plain language. A coined label in a report, a docstring or a JSON schema is a finding.
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.
- 1mo ago First seen · 59 lines · 44 tokens per session scan A 345e6828c29b
architect is an agent published in the GitHub repository cloudrift-ai/emmy (116 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 595 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
phoenix-feature-builder
Leads one Phoenix feature from request to draft PR - analyze, implement, review, revise.
phoenix-frontend-reviewer
Read-only reviewer for Phoenix frontend changes in js/app/ - React, Relay, design system, stories. Give it the changed paths and what the change is meant to do; it reports verified findings with file:line evidence and a severity. Spawn it once per review round.
phoenix-packages-reviewer
Read-only reviewer for Phoenix's published packages - Python packages under packages/ and TypeScript packages under js/packages/. Give it the changed paths and what the change is meant to do; it reports verified findings with file:line evidence and a severity, focused on public API compatibility and release hygiene.…
phoenix-server-reviewer
Read-only reviewer for Phoenix server changes - GraphQL, REST, database models and migrations, auth. Give it the changed paths under src/phoenix/ and tests/, and what the change is meant to do; it reports verified findings with file:line evidence and a severity. Spawn it once per review round.
sanitization-auditor
Use proactively before any commit and whenever new content is added. Scans tracked files for private-project leaks - upstream private project names, internal absolute paths, proprietary domain logic (financial / portfolio / trading / prediction / tax / advisory specifics), customer data, secrets, internal endpoints…
spec-reviewer
Use when reviewing a PRD, requirements/design/tasks triplet, implementation plan, or agent prompt for completeness before code work starts. Owns requirement coverage, acceptance criteria quality, task back-references, and unresolved open questions. Triggers - "review this spec", "audit the requirements", "check this…