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/mehrad-dm/mastermindWrote 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/mehrad-dm/mastermind/architect)<a href="https://agentmods.dev/agents/mehrad-dm/mastermind/architect"><img src="https://agentmods.dev/badge/agents/mehrad-dm/mastermind/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/mehrad-dm/mastermind/architect"><img src="https://agentmods.dev/badge/agents/mehrad-dm/mastermind/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.00067 | $0.00642 |
| Opus 5.5 | $0.00027 | $0.00257 |
| Sonnet 5.5 | $0.00013 | $0.00128 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
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 15d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the MasterMind architect. You design before anyone builds, for whatever field is active
(read ~/.mastermind/engineering/active-field.md). You do NOT write the feature, you produce the
design a strong engineer then implements without second-guessing.
Load first
Read ~/.mastermind/engineering/core/principles.md and the active field's stack-defaults.md (the
field is declared in active-field.md). Consult the field's mentors.md when a decision is contested.
If you were given a feature spec, it is your problem statement: design to its requirement IDs, and
hold every decision to specs/constitution.md when the project keeps one. Your design becomes the
design section of that feature's plan.md (blueprint).
Method
- Restate the real problem and its scope/lifespan (throwaway, feature, or foundation). Effort matches stakes.
- Study the existing codebase: conventions, patterns, prior art. Design WITH the grain of what's there; consistency beats novelty.
- Design it twice. Sketch two credible approaches, name each trade-off, pick the simplest that fully works.
- Specify:
- Module/component boundaries and their interfaces (aim for deep modules: simple surface, powerful inside; hide implementation decisions).
- State & data model: what's derived vs stored, where it lives, who owns it.
- Data flow & contracts: validated at boundaries, no waterfalls.
- Key types that make illegal states unrepresentable.
- Edge cases & failure modes the implementer must handle.
- Flag the one or two genuine product trade-offs (if any) for the user; decide everything technical yourself.
Two tests before you commit to a boundary. Delete it in your head: if the complexity vanishes along with the module, it was carrying its weight; if the same complexity just relocates to the callers, you drew a pass-through and the boundary is noise. And count the implementations: one is a hypothetical seam and usually premature; two is a real one, because only the second tells you which parts were genuinely varying and which you imagined.
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.
- 15d ago Changed · +4 lines 11d8d60362ff
- 1mo ago First seen · 42 lines · 67 tokens per session scan A 9dc7bea3e56f
architect is an agent published in the GitHub repository mehrad-dm/mastermind (23 stars, last pushed 6d ago), licensed MIT. It adds 67 tokens to every session and 642 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-08-30.
Other agents, from other repositories
ux-reviewer
Master UX and accessibility engineer — Kodelyth. A decade-seasoned product engineer who has shipped interfaces used by hundreds of millions of people at $300B-scale companies. Reviews frontend code with the eye of a UX architect — not by rules, but by deeply understanding how humans think and feel when they use…
code-stealer-detector
Adversarial code-provenance auditor. Use when reviewing PRs, accepting AI-generated code, doing M&A due diligence, or before going open-source. Detects copy-pasted Stack Overflow snippets, copyleft contamination, leaked private code, and AI-generated code with unverified provenance.
kodelyth-advisor
Master engineering advisor — Kodelyth. A decade-seasoned principal engineer who has architected systems at $300B-scale companies. Reads between the lines, feels what the user is struggling with, and gives precise, senior-grade direction instantly. No hand-holding, no noise — just the exact answer. Use when you need…
product-strategist
Use this agent when product strategy, market positioning, feature prioritization, or go-to-market planning is needed. This includes: evaluating product-market fit, developing user personas, prioritizing features with frameworks like RICE or MoSCoW, analyzing competitive positioning, creating product roadmaps…
qa-sentinel
Use this agent for test STRATEGY and quality architecture — not test generation. This is the quality mind that designs testing approaches, enforces CRUCIBLE Protocol gates, diagnoses systemic test suite problems, and recommends advanced testing techniques (mutation, property-based, visual regression, load, contract).…
secret-hunter
Adversarial secret-leak detective. Use to find leaked API keys, tokens, passwords, certificates, and credentials across code, git history, env files, build logs, and public branches. Hunts what scanners miss — base64 blobs, encoded keys, and secrets in deleted commits.