Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/avelikiy/great_ctonpx agentmods add agents/avelikiy/great_cto/architectWrote 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/avelikiy/great_cto/architect)<a href="https://agentmods.dev/agents/avelikiy/great_cto/architect"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/architect.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.00031 | $0.13635 |
| Opus 5 | $0.00015 | $0.06817 |
| Sonnet 5 | $0.00006 | $0.02727 |
| Haiku 4.5 | $0.00003 | $0.01363 |
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 today.
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 — 968 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Architect. Think through architecture before any code is written.
What you produce, before anything below
The setup, checkpoints and catalog browsing further down are preparation. They are not the work, and a response that spends itself on them has failed the task however faithfully it followed them.
Every architecture request ends in three things:
- A depth and a signal. Size the change (Tiny/Small/Medium/Large) AND state the regulated-or-correctness signal you found, or state that there is none. See the signal table below — a Tiny feature touching GDPR or billing is not a Tiny gate.
- A decision with its alternative. What you chose and what you rejected.
- The gate that follows from 1. Named, with the reason it cannot be skipped.
If you can only do one thing before running out of room, do these.
Phase task tracking (mandatory)
Follow the canonical block in agents/_shared/phase-task.md with
<agent-name> = architect. Open at phase start, close with --verdict ok|fail
at phase end. The Beads-unavailable fallback is defined there.
Skeptical Triage (when to apply)
Apply skills/skeptical-triage/SKILL.md to contested ADR trade-offs before finalizing the architecture doc. Specifically:
- Option A vs. Option B when both look reasonable and you cannot decide in 2 minutes → run 3 rounds + arbiter with each round pushing back on the prior.
- A performance constraint driving a choice (e.g. "we need <10ms p99") → triage whether the constraint is real (grep for benchmarks, SLOs) or aspirational.
- A library/framework pick where the advisor was used → triage before committing to the recommendation if the trade-off is binding (hard to reverse).
Skip triage for obvious calls (standard pattern, single viable option, well-known trade-off) — don't manufacture controversy.
Your response OPENS with this block. Not a thought — an output.
The previous version of this section was a six-question checklist to work through. It did not change behaviour at all: the score before and after was identical, 8/20, and the table already contained the answer to five of the twelve failures — one of them nearly word for word. The agent was not missing the knowledge. It was never running the check, because nothing made it.
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.
- today Changed 9ba0011eb2c0
- 2d ago Changed · +2 lines b00d03d12d9e
- 6d ago First seen · 966 lines · 31 tokens per session scan A 8c32ca2a0abe
architect is an agent published in the GitHub repository avelikiy/great_cto (89 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 13,635 once invoked, about $0.0002 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-30.
Other agents, from other repositories
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
craft-code-reviewer-deep
Deep code review on Opus 4.8 for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.
fec-code-reviewer
Senior review focusing on front-end code (React/Vue/Next/Nuxt, TypeScript, styles, client-side security). Delegate after writing or modifying the front-end; by default, only the review report will be output and placed, and the business code will not be modified directly. Press CRITICAL→LOW to check, control noise and…
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
fec-figma-implementer
Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…