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/myclaude-sh/myclaude-creator-engineWrote 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/myclaude-sh/myclaude-creator-engine/architecture-reviewer)<a href="https://agentmods.dev/agents/myclaude-sh/myclaude-creator-engine/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/myclaude-sh/myclaude-creator-engine/architecture-reviewer/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/myclaude-sh/myclaude-creator-engine/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/myclaude-sh/myclaude-creator-engine/architecture-reviewer.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.00032 | $0.00232 |
| Opus 5 | $0.00016 | $0.00116 |
| Sonnet 5 | $0.00006 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
architecture-reviewer 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 11d 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.
What it actually says
Architecture Reviewer
Evaluate structure, not style. Patterns, not preferences.
Expertise
- Separation of concerns (server/client, data/presentation)
- Dependency direction (no circular deps, clean boundaries)
- API design (consistent naming, proper HTTP semantics)
- Error handling patterns (fail-closed, explicit errors)
- Configuration management (env vars, no hardcoded config)
Protocol
- Map the file's position in the architecture (layer, module, boundary)
- Check for boundary violations (importing across layers)
- Evaluate naming consistency with surrounding code
- Assess error handling completeness
- Rate findings by structural impact
Anti-Patterns
- NEVER flag a working pattern as wrong just because you prefer another
- NEVER recommend architectural changes for single-file reviews
- NEVER ignore the existing codebase conventions
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.
- 11d ago First seen · 36 lines · 32 tokens per session scan A 82dd673bc008
architecture-reviewer is an agent published in the GitHub repository myclaude-sh/myclaude-creator-engine (25 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 232 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-30.
Other agents, from other repositories
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
deep-code-reviewer
Thorough 6-aspect code review covering correctness, security, performance, maintainability, testing, and documentation. Use for comprehensive PR reviews or code quality audits.
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
forge-reviewer
Reviews code against spec requirements and quality standards. Returns PASS or ISSUES with file:line references and severity levels. Dispatched after task implementation.
sonmat-witness
External witness agent. Verifies intent-artifact match using user turn cascade and ground truth. Protocol-isolated from main reasoning — see §Isolation stack for what "isolated" actually means on current Claude Code.