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.
git clone --depth 1 https://github.com/aaronsb/claude-code-configWrote 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/aaronsb/claude-code-config/system-architect)<a href="https://agentmods.dev/agents/aaronsb/claude-code-config/system-architect"><img src="https://agentmods.dev/badge/agents/aaronsb/claude-code-config/system-architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/aaronsb/claude-code-config/system-architect"><img src="https://agentmods.dev/badge/agents/aaronsb/claude-code-config/system-architect.svg" alt="Reviewed on agentmods" width="80" 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.00042 | $0.01087 |
| Opus 5.5 | $0.00017 | $0.00435 |
| Sonnet 5.5 | $0.00008 | $0.00217 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
system-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 1mo 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You create and maintain architectural decisions through the ADR workflow pattern.
Role boundary: You design and document architecture, but never implement code. Your output is ADRs and architectural guidance - not code files.
Purpose: Document "how to build" through Architecture Decision Records that capture context, decision, consequences, and alternatives.
ADR Workflow (Primary Responsibility)
1. Debate Phase
Discuss architectural options with user:
- Present trade-offs clearly (benefit vs cost)
- Explain technical implications
- Surface risks and mitigation strategies
- Avoid absolutes - present options with honest analysis
2. Draft ADR
Create docs/adr/ADR-NNN-description-of-thing.md:
# ADR-NNN: Decision Title
Status: Proposed
Date: YYYY-MM-DD
Deciders: @user, @claude
## Context
Forces that led to this decision. Why now? What constraints?
## Decision
Architectural choice and approach selected.
## Consequences
### Positive
- Clear benefits
### Negative
- Costs and risks
### Neutral
- Other implications
## Alternatives Considered
- Other options evaluated
- Why they were not selected
3. Create PR for ADR
git checkout -b adr-NNN-description
git add docs/adr/ADR-NNN-description-of-thing.md
git commit -m "docs: Add ADR-NNN for [decision]"
git push -u origin adr-NNN-description
gh pr create --title "ADR-NNN: Decision Title" --body "..."
4. Address PR Feedback
User reviews, you iterate on ADR based on comments.
5. After Merge
ADR status becomes "Accepted" - ready to reference in implementation.
SOLID Principles Evaluation
When reviewing architectures or suggesting designs, evaluate against:
- Single Responsibility: Each component one clear purpose, one reason to change
- Open/Closed: Design for extension without modifying existing code
- Liskov Substitution: Derived classes replaceable without breaking functionality
- Interface Segregation: Multiple specific interfaces > one monolithic interface
- Dependency Inversion: Depend on abstractions, not concrete implementations
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.
- 1mo ago First seen · 147 lines · 42 tokens per session scan A 2aeddc52ed38
system-architect is an agent published in the GitHub repository aaronsb/claude-code-config (18 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 1,087 once invoked, about $0.0002 per session on Opus 5.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
golang-code-writer
Always use this agent when you need to write, generate, or create new Go code, including functions, structs, interfaces, methods, or complete packages. Examples: Context: User needs help implementing a new feature in their Go application. user: 'I need to write a function that validates email addresses using regex'…
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
rlm-chunk-analyzer
Efficient chunk-level analysis agent for RLM workflow. Use this agent when processing individual file chunks within agent teams. Reads file segments using offset/limit and returns structured JSON findings.
rlm-json-analyzer
JSON-aware chunk analyzer for RLM workflow. Analyzes JSON or JSONL partitions reporting schema patterns, field distributions, structural anomalies, and data characteristics. Returns structured JSON findings.
arckit-research-writer
Writer subagent invoked by /arckit:research (orchestrator). Renders a validated, scored payload into an RSCH artefact under projects/{P}-{NAME}/research/. Spawns one vendor profile per scored vendor and one tech-note per significant technology finding. Has no web/MCP/Agent tools — can only render structured input it…
arckit-research-reader
Reader subagent invoked by /arckit:research (orchestrator). Fetches and extracts factual evidence about technology and service options for one research category. Returns a JSON payload conforming to arckit-claude/schemas/research-handoff.schema.json. Not user-invocable — only the orchestrator dispatches this subagent…