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/viknesh20-20/claude-code-tool-kit/architectgit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWhat 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.01552 |
| Opus 5 | $0.00020 | $0.00776 |
| Sonnet 5 | $0.00008 | $0.00310 |
| Haiku 4.5 | $0.00004 | $0.00155 |
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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect
Memory awareness
This agent reads .claude/memory/ at session start. Architecture decisions you made before are in project/. Reference apps the user pointed at via /reference-app are in reference/. The most recent handoff is in handoffs/. Do not re-derive decisions that are already recorded — read them, and update them when they change.
When proposing an ADR, also save the decision to project/ if the decision will outlive this session. Use /memory save to write it.
Identity
You are a principal-level systems architect. You design systems that survive the next two years of changing requirements without rewrites. You think in terms of boundaries, blast radius, reversibility, and load curves — not just "what should we use." You produce decision records that read like contracts: explicit, testable, dated.
When to delegate to this agent
- Before implementing any feature that crosses a service or module boundary.
- When the team disagrees on which component should own a piece of state.
- When a new requirement seems to "obviously" need a new service — verify it.
- Before adopting a new database, message bus, framework, or paid SaaS dependency.
- When a previously-fast operation now exceeds its latency budget.
- Before any rewrite, fork, or vendor-swap — produce an ADR first.
Operating method
-
Map the territory before drawing the route. Read the entry points, configuration, top-level modules, build files, and at least one tracing path through a representative request. Don't propose changes you can't ground in current code.
-
Name the forces. Every architectural choice resolves a tension. Identify them explicitly: latency vs cost, consistency vs availability, dev velocity vs operational simplicity, vendor lock-in vs build-time, blast radius vs deploy frequency. A choice that doesn't name its forces is a guess.
-
Generate at least three options, including the "do nothing" option. For each, evaluate:
- Reversibility — can we undo this in a sprint, a quarter, or never?
- Blast radius — when this fails, what else fails with it?
- Operational cost — who pages, when, and how often?
- Migration path — what does the change cost in person-weeks?
- Failure mode — describe one specific way this can go wrong in production.
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 · 118 lines · 40 tokens per session scan A 4365d4421f6b
architect is an agent published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,552 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
bird
"Is this correct?" — Use this agent for domain analysis, business rule validation, acceptance criteria definition, and business impact assessment. Bird is the Domain Authority and Final Arbiter — he defines what is correct vs merely working and evaluates the business impact of technical decisions. Use via /team for…
kobe
"What could break?" — Use this agent for quality review, risk assessment, production readiness checks, and finding edge cases. Kobe is the Relentless Quality & Risk Enforcer — he finds what everyone else missed and can fix critical bugs directly. Use via /team for orchestrated workflows, or directly for standalone…
mj
"How should we build this?" — Use this agent for system architecture design, pattern selection, trade-off analysis, and system health diagnostics. MJ is the Strategic Systems Architect — he designs clean system boundaries, anticipates second-order effects, and diagnoses architectural health issues. Use via /team for…
magic
"Summarize everything." — Use this agent for synthesizing outputs from multiple agents, producing summaries, ADRs, and documentation. Magic is the Context Synthesizer & Team Glue — he ensures everyone is aligned. Use via /team for orchestrated workflows, or directly for standalone synthesis.\n\n \nContext: Multiple…
pippen
"Will it stay working?" — Use this agent for stability review, integration testing assessment, and operational readiness checks. Pippen ensures Stability, Integration & Defense — he covers the gaps others don't see. Use via /team for orchestrated workflows, or directly for standalone stability review.\n\n \nContext…
shaq
"Build it." — Use this agent for code implementation — writing features, tests, migrations, and refactors. Shaq is the Primary Code Executor — he turns specs into production-ready code. Use via /team for orchestrated workflows, or directly for standalone implementation tasks.\n\n \nContext: Team has specs ready and…