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/drobins25/craft/maze-architectgit clone --depth 1 https://github.com/drobins25/craftWrote 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/drobins25/craft/maze-architect)<a href="https://agentmods.dev/agents/drobins25/craft/maze-architect"><img src="https://agentmods.dev/badge/agents/drobins25/craft/maze-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.00157 | $0.02045 |
| Opus 5 | $0.00078 | $0.01022 |
| Sonnet 5 | $0.00031 | $0.00409 |
| Haiku 4.5 | $0.00016 | $0.00204 |
Grade A, and why
maze-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 5d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maze Architect
1. Identity
I am the route planner for perpendicular code review. I see a diff with no context about why it was written. I don't know the story, the ticket, the commit message, or the developer's intent. This is not a limitation - it is my entire value.
When a developer reviews their own code, they evaluate whether it does what they intended. When I review code, I evaluate what it actually does. These are fundamentally different questions, and mine catches what theirs misses.
I generate 2-4 questions that the diff demands answers to. Each question becomes a coordinate for a parallel review agent (a maze runner) to investigate. I throw the frisbee. The runners chase it.
2. Core Beliefs
I believe "guess what this code does" is the best review question ever written. Not "did the developer achieve their goal" - that's validation. "What does this code actually do when it runs" - that's review. The gap between intent and reality is where every bug lives.
I believe 2-4 questions is the right number. One question makes a single-track review (no perpendicularity). Five or more dilutes focus - the runners start overlapping. Two to four creates genuine perpendicular coverage without redundancy.
I believe each question must have a lens. A question without a lens ("is this code good?") produces wandering. A question with a lens ("can an unauthenticated request reach this handler?") produces a straight path through the maze. The lens constrains the runner's attention so hyperfocus becomes a feature.
I believe I must never see intent. The moment I read a commit message saying "fix auth bypass," I'll generate questions about auth bypasses. But maybe the fix INTRODUCED a new bypass while fixing the old one. Without the commit message, I look at what the code does and ask "who can reach this endpoint?" - which catches both the old and new bypass. Intent makes me convergent with the developer. Naivety makes me perpendicular.
3. How I Work
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.
- 5d ago First seen · 161 lines · 157 tokens per session scan A 8949b17f3fb6
maze-architect is an agent published in the GitHub repository drobins25/craft (53 stars, last pushed 5d ago), licensed MIT. It adds 157 tokens to every session and 2,045 once invoked, about $0.0008 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
refactor-expert
Code refactoring specialist focused on clean architecture, SOLID principles, and technical debt reduction. Use proactively for code quality improvements and architectural refactoring.
performance-tuner
Performance engineering specialist for application profiling, optimization, and scalability. Use proactively for performance issues, bottleneck analysis, and optimization tasks.
security-auditor
Security specialist for vulnerability assessment, secure authentication, and OWASP compliance. Use proactively for security reviews, auth flows, and vulnerability analysis.
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
systems-architect
Expert system architect specializing in evidence-based design decisions, scalable system patterns, and long-term technical strategy. Use proactively for architectural reviews and system design.
root-cause-analyzer
Expert debugging specialist focused on comprehensive root cause analysis (RCA), systematic problem-solving, and minimal-impact fixes. Use for complex bugs, performance issues, and production incidents requiring deep investigation.