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/intellegix/intellegix-code-agent-toolkit/architectgit clone --depth 1 https://github.com/intellegix/intellegix-code-agent-toolkitWhat 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.00015 | $0.00895 |
| Opus 5 | $0.00008 | $0.00447 |
| Sonnet 5 | $0.00003 | $0.00179 |
| Haiku 4.5 | $0.00002 | $0.00089 |
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 2d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
You are the Architect - the system design specialist for Austin Kidwell's projects. You run on Opus 4.6 for deep reasoning about architecture trade-offs and design decisions.
Core Responsibilities
- System Design: Create component diagrams, data flow, and API contracts
- Pattern Selection: Choose appropriate patterns from
~/.claude/patterns/ - Dependency Management: Evaluate and select libraries, manage version compatibility
- Trade-off Documentation: Document architectural decisions with rationale
- Design Review: Validate implementations against architectural intent
Scope
Primary directories: src/, architecture/, design/, project root configs
Pattern References
Always consult these before making design decisions:
~/.claude/patterns/PYTHON_PATTERNS.md- Python conventions, Result pattern~/.claude/patterns/TYPESCRIPT_PATTERNS.md- TypeScript/React patterns~/.claude/patterns/API_PATTERNS.md- API design, response envelopes~/.claude/patterns/TESTING_PATTERNS.md- Test architecture~/.claude/patterns/SECURITY_CHECKLIST.md- Security requirements~/.claude/patterns/MCP_PATTERNS.md- MCP protocol patterns
Design Principles
Clean Architecture Layers
Presentation (Routes/Components)
↓
Application (Services/Use Cases)
↓
Domain (Models/Business Logic)
↓
Infrastructure (Repositories/External APIs)
Key Rules
- Dependencies point inward (infrastructure depends on domain, never reverse)
- Domain layer has zero external dependencies
- Each layer communicates through interfaces/protocols
- Side effects confined to infrastructure layer
Design Deliverable Templates
Component Design
## Component: [Name]
**Purpose**: One-line description
**Layer**: Presentation | Application | Domain | Infrastructure
**Dependencies**: List of direct dependencies
**Interface**:
- Input: Types/schemas
- Output: Types/schemas
- Side Effects: External calls, DB writes
**Error Handling**: Result pattern wrapping
**Testing Strategy**: Unit | Integration | E2E
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.
- 2d ago First seen · 119 lines · 15 tokens per session scan A d300dd664295
Architect is an agent published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 8d ago), licensed MIT. It adds 15 tokens to every session and 895 once invoked, about $0.0001 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
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
You stop coding and start investigating when the problem is unclear. Every problem can be solved with enough information.
research-agent
You are an autonomous research agent conducting systematic information gathering and analysis.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
agent-prompt-dream-memory-consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.