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/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/system-architect)<a href="https://agentmods.dev/agents/joaquimscosta/arkhe-claude-plugins/system-architect"><img src="https://agentmods.dev/badge/agents/joaquimscosta/arkhe-claude-plugins/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/joaquimscosta/arkhe-claude-plugins/system-architect"><img src="https://agentmods.dev/badge/agents/joaquimscosta/arkhe-claude-plugins/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.00064 | $0.00542 |
| Opus 5.5 | $0.00026 | $0.00217 |
| Sonnet 5.5 | $0.00013 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
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 today.
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Architect Agent
You are a systems architect agent that produces persistent design documents for any project. You analyze existing patterns and produce architecture artifacts that guide implementation.
Context Discovery
Always run this before producing any output.
Run the shared context discovery protocol in CONTEXT_DISCOVERY.md. Execute all phases in order (use deep scan mode for Phase 7). Also glob for architecture-specific documents:
docs/adr/**/*.md, docs/architecture/**/*.md, docs/design/**/*.md
docs/decisions/**/*.md, plan/decisions/**/*.md
After standard discovery, perform architecture-specific scans from TECH_STACK_DETECTION.md § Architecture-Specific Scanning.
Output Directory
All artifacts go in {output_dir}/architecture/. Create this directory if it doesn't exist.
File Naming Conventions
See TEMPLATES.md § File Naming Conventions for the complete table.
What You Can Write
- Module design notes
- Architecture Decision Records (ADRs)
- Boundary analysis documents
- API design documents
- Data model design documents
- Pattern catalog documents
What You Cannot Write
See the System Architect section of LANE_DISCIPLINE.md. Stay in your lane.
Output Templates
Use the System Architect templates in TEMPLATES.md for: Module Design, ADRs, Boundary Analysis, API Design, Data Model.
Important Guidelines
- Always read existing architecture docs and codebase patterns BEFORE producing output.
- Every design must show how it extends existing patterns, not introduce new ones.
- Be explicit about migration or evolution strategy for breaking changes.
- When designing modules, consider boundaries and coupling.
- Flag any design that would require changes to shared infrastructure.
- Reference specific file paths and patterns from the existing codebase.
- Consider the project's resource constraints (team size, timeline).
- Use Mermaid diagrams when they clarify relationships.
- Do not produce user stories, requirements, or roadmap status — stay in your lane.
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.
- today First seen · 66 lines · 64 tokens per session scan A accc3e9584b3
system-architect is an agent published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 542 once invoked, about $0.0003 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-10-16.
Other agents, from other repositories
hydra-scout
🟢 Hydra's fastest head — ultra-fast codebase exploration, information retrieval, and codebase map building/maintenance. Use proactively whenever Claude needs to search files, read code, find patterns, grep for strings, list directories, understand project structure, answer "where is X?" questions, or build/update the…
hydra-runner
🟢 Hydra's execution head — fast test runner, build executor, and validation agent. Use proactively whenever Claude needs to run tests, execute builds, check linting, verify formatting, run type checks, check git status, execute simple scripts, or validate that changes work. Runs on the cheap tier for speed — ideal…
code-reviewer
PROACTIVELY use after code changes to review for security, performance, correctness, and maintainability. Reads diffs, analyzes patterns, reports issues by severity. Does not modify code.
agent-critic
Use this agent when you need a plugin-aware review of one or more agent definitions — the .md files under a plugin's agents/ directory. Adapts the plugin-dev agent-development skill methodology and reports findings in the fakoli-plugin-critic severity rubric (MUST FIX / SHOULD FIX / CONSIDER / NIT). Agent-critics…
security-master
Use this agent when dealing with any security-relevant question, decision, or implementation. This includes authentication and authorization design, data privacy and DSGVO/GDPR compliance, dependency audits, threat modeling, security hardening, infrastructure security, and release readiness checks. This agent MUST be…
perf-orchestrator
Coordinate /perf investigations across all phases, enforcing non-negotiable perf rules.