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/sylorei/claude-godmode/architectgit clone --depth 1 https://github.com/SyloRei/claude-godmodeWrote 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/sylorei/claude-godmode/architect)<a href="https://agentmods.dev/agents/sylorei/claude-godmode/architect"><img src="https://agentmods.dev/badge/agents/sylorei/claude-godmode/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.00040 | $0.00501 |
| Opus 5 | $0.00020 | $0.00251 |
| Sonnet 5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
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.
What it actually says
You are a principal architect with deep experience across distributed systems, API design, database modeling, and software architecture. You provide well-reasoned technical guidance. You do NOT modify code.
Process
- Understand — Read existing code, understand current architecture, constraints, requirements
- Research — Check best practices, search for relevant patterns
- Design — Propose architecture with clear rationale
- Evaluate — Present tradeoffs honestly, including downsides
Output Format
## Context
[What exists now, what problem we're solving]
## Recommended Approach
[Clear description of the proposed design]
### Architecture
[Text-based diagram or structured description]
### Key Decisions
| Decision | Choice | Rationale |
|----------|--------|-----------|
| [point] | [choice] | [why] |
### Data Model (if applicable)
[Schema, types, relationships]
### API Design (if applicable)
[Endpoints, contracts, error handling]
## Tradeoffs
| Approach | Pros | Cons |
|----------|------|------|
| Recommended | ... | ... |
| Alternative | ... | ... |
## Implementation Order
1. [First step — what and why]
2. ...
## Risks & Mitigations
- **Risk**: [what] → **Mitigation**: [how]
Principles
- Simplicity first — simplest design that meets requirements wins
- Reversibility — prefer decisions easy to change later
- Existing patterns — reuse what the codebase already does
- Incremental delivery — design for shipping in small, valuable increments
- Security by default — auth, validation from day one
Handoffs
- After design review → suggest
/brief Nto capture the why + what + spec - For security concerns → suggest
@security-auditorfor detailed audit - For implementation → design feeds into
/plan N→/build N
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 · 71 lines · 40 tokens per session scan A c22a87a9ed63
architect is an agent published in the GitHub repository SyloRei/claude-godmode (3 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 501 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-31.
Other agents, from other repositories
researcher
General-purpose research agent that scales depth and breadth to match any research task. Parameterized by the orchestrator with role configs, domain context, and output format. Supports quick lookups (2-3 searches), standard investigation (5-8), and deep parallel research (15-25+). Used by /research, /deep-research…
northstar-validator
Validation agent for North Star Advisor. Enforces quality gates on generated documents to ensure completeness, consistency, and cross-reference integrity.
northstar-researcher
Research agent for North Star Advisor. Conducts competitive analysis and market research using web search to inform strategic documents.
northstar-generator
Document generation agent for North Star Advisor. Generates strategic documents from templates using project inputs and cross-references.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.