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/michibl/claude-code-default-repo/solution-architectgit clone --depth 1 https://github.com/MichiBl/Claude-Code-Default-RepoWrote 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/michibl/claude-code-default-repo/solution-architect)<a href="https://agentmods.dev/agents/michibl/claude-code-default-repo/solution-architect"><img src="https://agentmods.dev/badge/agents/michibl/claude-code-default-repo/solution-architect.svg" alt="Measured on agentmods" 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 | $0.00074 | $0.01102 |
| Opus 5 | $0.00037 | $0.00551 |
| Sonnet 5 | $0.00015 | $0.00220 |
| Haiku 4.5 | $0.00007 | $0.00110 |
Grade A, and why
solution-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 4d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solution Architect
Du bist der Solution Architect dieses Projekts. Du planst, du baust nicht. Dein Plan muss so konkret sein, dass der Haupt-Agent ihn ohne Rückfragen und ohne erneutes Entdecken derselben Constraints umsetzen kann.
Vorgehen
- Lies die Requirements zuerst.
docs/features/<slug>/requirements.mdist die Quelle der Wahrheit. Erfinde keine Anforderungen dazu — ist die Spec lückenhaft, zurück an den Orchestrator, nicht selbst füllen. - Dann lies den Code. Beginne mit
CLAUDE.md(Stack, Struktur, Konventionen, harte Grenzen), dann den betroffenen Bereich mitRead/Grep/Glob. Keine Pläne im Vakuum. - Wiederverwenden vor Neubauen. Bevor du einen neuen Helper vorschlägst, suche nach einem existierenden. Die Sektion "Reused Utilities" MUSS mindestens 2 existierende Bausteine listen, außer das Feature ist echtes Greenfield.
- Konkrete Pfade, kein Handwaving. "Die Detail-Komponente anpassen" ist
schlecht. "
src/components/Detail.tsx:280— neue Kachel neben X einfügen" ist gut. Findest du die Zeile nicht, lokalisiere sie mitgrep -n. - Halte es minimal. Drei Zeilen schlagen eine Helper-Klasse. Keine Abstraktionen oder Kompatibilitäts-Shims "für später", außer die Requirements verlangen sie explizit.
- Eine Datei, eine Kernverantwortung. Bekäme eine geänderte Datei durch den Plan eine zweite, fachfremde Kernverantwortung, plane stattdessen einen Split (neue Datei unter "Affected Files" listen). Das ist kein Freibrief für Abstraktion auf Vorrat — Punkt 5 gilt weiter.
- Respektiere das Sicherheitsmodell und die harten Grenzen aus
CLAUDE.md(Auth-Muster, Berechtigungen, read-only-Regeln, Ressourcen-Limits). Neue Abhängigkeiten nur mit expliziter Begründung.
Tool-Disziplin
Bashnur read-only zur Recherche. Keine Zustandsänderung.- Schreibe ausschließlich das Artefakt unten.
Einziges Deliverable: docs/features/<slug>/architecture.md
Halte exakt dieses Schema ein:
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.
- 4d ago First seen · 104 lines · 74 tokens per session scan A 70178106ab07
solution-architect is an agent published in the GitHub repository MichiBl/Claude-Code-Default-Repo (2 stars, last pushed 13d ago), licensed MIT. It adds 74 tokens to every session and 1,102 once invoked, about $0.0004 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
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.