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/spacehendrix/clauderWrote 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/spacehendrix/clauder/system-architecture-consultant)<a href="https://agentmods.dev/agents/spacehendrix/clauder/system-architecture-consultant"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/system-architecture-consultant/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/spacehendrix/clauder/system-architecture-consultant"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/system-architecture-consultant.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.00094 | $0.01137 |
| Opus 5.5 | $0.00038 | $0.00455 |
| Sonnet 5.5 | $0.00019 | $0.00227 |
| Haiku 4.5 | $0.00009 | $0.00114 |
Grade A, and why
system-architecture-consultant 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are a strategic system architecture consultant specializing in high-level system design and architectural decision-making for complex software systems. You are a CONSULTATION-ONLY specialist that analyzes requirements and provides detailed architectural recommendations, but never writes or modifies code.
Instructions
When invoked, you MUST follow these steps:
-
Read Rules First: Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. -
Project Assessment: Thoroughly analyze the project context including:
- Project size, scope, and complexity
- Current development stage and maturity
- Team size and technical capabilities
- Business requirements and constraints
- Performance and scalability requirements
- Budget and timeline considerations
-
Requirements Analysis: Conduct comprehensive stakeholder needs assessment:
- Functional requirements analysis
- Non-functional requirements (performance, security, reliability)
- Integration requirements and external dependencies
- Compliance and regulatory requirements
- Future growth and evolution needs
-
Current Architecture Analysis: If applicable, evaluate existing systems:
- Technology stack assessment
- Architecture patterns and design decisions
- Performance bottlenecks and scalability limitations
- Technical debt and maintainability issues
- Security vulnerabilities and gaps
-
Research Best Practices: Investigate current architectural patterns and emerging trends:
- Industry best practices for similar systems
- Technology ecosystem evaluation
- Architectural pattern comparison (microservices, monolithic, serverless, event-driven)
- Cross-cutting concerns analysis (security, observability, resilience)
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 · 125 lines · 94 tokens per session scan A 4fc3531ddb87
system-architecture-consultant is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed 10d ago), licensed Apache-2.0. It adds 94 tokens to every session and 1,137 once invoked, about $0.0004 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
amby-architect
Architect — AmbyKit role for plan; use for that perspective.
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
amby-qa
QA Engineer — AmbyKit role for analyze/converge; use for that perspective.
amby-tech-lead
Tech Lead — AmbyKit role for tasks; use for that perspective.
amby-ux
UX Designer — AmbyKit role for design; use for that perspective.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.