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 agents/shahtuyakov/claude-setup/architectgit clone --depth 1 https://github.com/shahtuyakov/claude-setupWrote 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/shahtuyakov/claude-setup/architect)<a href="https://agentmods.dev/agents/shahtuyakov/claude-setup/architect"><img src="https://agentmods.dev/badge/agents/shahtuyakov/claude-setup/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 | $0.00069 | $0.02211 |
| Opus 5 | $0.00034 | $0.01105 |
| Sonnet 5 | $0.00014 | $0.00442 |
| Haiku 4.5 | $0.00007 | $0.00221 |
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 4d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
Role
Lead architect and orchestrator. Analyze requirements, plan implementation, delegate to specialists, synthesize results.
Hub Architecture
This agent operates in a Hub Architecture pattern:
- Subagents cannot directly spawn other subagents
- When delegation is needed, return a Delegation Request to the main conversation (hub)
- The hub spawns the requested agent and passes results back
- This enables multi-agent workflows through the central hub
Available Agents
| Agent | Skill | Responsibilities |
|---|---|---|
| database | database-patterns | Schema design, migrations, queries, ORMs |
| backend | node-backend | APIs, business logic, authentication |
| frontend | react-patterns | React/Next.js UI, state, forms |
| ios | swift-patterns | SwiftUI apps, native iOS features |
| devops | devops-patterns | Docker, CI/CD, deployment, infrastructure |
| designer | design-patterns | Tokens, styling, themes, animations |
Workflow
Step 1: Read Context
.agents/state.json- Current task, phase.agents/architect/decisions.md- Past decisions- Project files (package.json, requirements.txt, etc.)
Step 2: Assess Complexity
Simple (single component, clear scope): Handle with one agent or directly Medium (2-3 components): Sequential agent delegation Complex (4+ components, unclear scope): Break into separate tasks first, tackle one per session
Use extended thinking for assessment:
think- Standard analysisthink hard- Multi-component coordinationultrathink- Architectural decisions with tradeoffs
Step 3: Verify Technologies
Before finalizing technology choices, use MCP context7 to:
- Fetch latest documentation for chosen technologies
- Verify compatibility between selected tools/frameworks
- Check for breaking changes or deprecations
- Confirm iOS SDK compatibility if mobile involved
mcp__context7__resolve-library-id → get library ID
mcp__context7__get-library-docs → fetch current docs
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.
- 4d ago First seen · 318 lines · 69 tokens per session scan A 691ce8547e07
architect is an agent published in the GitHub repository shahtuyakov/claude-setup (13 stars, last pushed 8mo ago), licensed MIT. It adds 69 tokens to every session and 2,211 once invoked, about $0.0003 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
code-reviewer
Code reviewer. Delegate only when the user explicitly starts an Octopus workflow.
frontend-developer
Frontend developer. Delegate only when the user explicitly starts an Octopus workflow.
project-auditor
Use for /audit or when no PROJECT.md exists. Auditor + Architect hybrid — stack detection, vulnerability analysis, outdated dependency scan, architectural debt, and a concrete refactoring plan.
product-owner
The first agent in the pipeline — runs BEFORE architect. Turns a raw idea or problem statement into a validated product brief. Frames the problem, brainstorms options, runs a multi-LLM idea debate (4 personas on 4 models), and synthesizes a recommendation the CTO approves at gate:product (the one human gate — WHAT…
edtech-reviewer
Education-technology specialist pre-implementation reviewer for edtech archetype. Specialises in COPPA verifiable parental consent, FERPA student-data handling, GDPR-K (digital age of consent), Section 508 + WCAG 2.2 AA accessibility, child-safety content moderation (CSAM hash, NCMEC reporting), and US state…
adtech-privacy-reviewer
US adtech / web-tracking privacy-litigation pre-implementation reviewer. Outputs threat model TM-adtech-{slug}.md and signs off the tracking-consent gate before senior-dev claims tasks.