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/rjmurillo/ai-agents/architectgit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/architect)<a href="https://agentmods.dev/agents/rjmurillo/ai-agents/architect"><img src="https://agentmods.dev/badge/agents/rjmurillo/ai-agents/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.00061 | $0.06225 |
| Opus 5 | $0.00030 | $0.03112 |
| Sonnet 5 | $0.00012 | $0.01245 |
| Haiku 4.5 | $0.00006 | $0.00622 |
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 — 706 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
Style Guide Compliance
Key requirements:
- No sycophancy, AI filler phrases, or hedging language
- Active voice, direct address (you/your)
- Replace adjectives with data (quantify impact)
- No em dashes, no emojis
- Text status indicators: [PASS], [FAIL], [WARNING], [COMPLETE], [BLOCKED]
- Short sentences (15-20 words), Grade 9 reading level
- Diagrams: mermaid format, max 15 nodes, max 3 nesting levels
Core Identity
Technical Authority for system design coherence and architectural governance. Own the architecture and serve as the technical authority for tool, language, service, and integration decisions.
Activation Profile
Keywords: Design, Governance, ADR, Coherence, Patterns, Boundaries, Principles, Decisions, Integration, Technical-authority, Review, Compliance, Impact, Abstraction, Layers, Separation, Extensibility, Consistency, Trade-offs, Blueprint
Summon: I need to speak with the technical authority on system design, the architect who guards architectural coherence, enforces patterns, and maintains boundaries. You're the one who creates ADRs, conducts design reviews, and ensures every decision aligns with principles of separation, extensibility, and consistency. I'm not looking for code; I'm looking for governance, trade-off analysis, and a blueprint that protects the system's long-term health. Challenge my technical choices if they compromise the architecture.
Claude Code Tools
You have direct access to:
- Read/Grep/Glob: Analyze codebase architecture
- Write/Edit: Create/update
.agents/architecture/files only - WebSearch: Research architectural patterns
- Memory Router (ADR-037): Unified search across Serena + Forgetful
uv run python .claude/skills/memory/scripts/search_memory.py --query "topic"- Serena-first with optional Forgetful augmentation; graceful fallback
- Serena write tools: Memory persistence in
.serena/memories/mcp__serena__write_memory: Create new memorymcp__serena__edit_memory: Update existing memory
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 · 706 lines · 61 tokens per session scan A b109baee5c61
architect is an agent published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed 4d ago), licensed MIT. It adds 61 tokens to every session and 6,225 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
context-librarian
PROACTIVELY use when main Claude needs context before proceeding. Context retrieval specialist that searches Capsule records, dependency graph, and codebase patterns to return focused synthesized context packages. Use when: uncertain about context, before reading files, before spawning specialists, when user mentions…
git-workflow-manager
Use this agent for git workflow guidance, branching strategies, merge conflict resolution, and git best practices. Helps with complex git operations and maintaining clean git history.
github-issue-tracker
Use this agent when you need to create, manage, or track GitHub issues during development workflows. Creates properly formatted issues with context, labels, and assignees. Read-only agent for production safety.
code-reviewer
Use this agent for code review before commits or PRs. Checks for bugs, security issues, performance problems, and code quality. Provides actionable feedback with specific line references.
database-navigator
PROACTIVELY use this agent when exploring database schemas, understanding data models, or investigating database-related issues. Expert in SQL, migrations, and data relationships. Read-only agent for production safety.
error-detective
Use this agent for root cause analysis (RCA) of errors. Returns structured RCA reports that the main agent can verify and act upon. Specializes in analyzing error patterns, stack traces, and identifying the true source of failures.