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/plugins/mehrad-dm/mastermind/mastermind)<a href="https://agentmods.dev/plugins/mehrad-dm/mastermind/mastermind"><img src="https://agentmods.dev/badge/plugins/mehrad-dm/mastermind/mastermind/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/plugins/mehrad-dm/mastermind/mastermind"><img src="https://agentmods.dev/badge/plugins/mehrad-dm/mastermind/mastermind.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mastermind 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 14d 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
{
"$schema": "https://www.schemastore.org/claude-code-plugin-manifest.json",
"name": "mastermind",
"description": "A markdown brain that gives your AI coding tools judgment and rigor: sharp defaults, real decisions, and the discipline to verify before saying done. For Claude Code, Cursor and Codex.",
"version": "0.33.2",
"hooks": "./hooks/hooks.json",
"author": {
"name": "mehrad-dm"
},
"homepage": "https://mastermind.mehrad.me",
"repository": "https://github.com/mehrad-dm/mastermind",
"license": "MIT",
"keywords": [
"skills",
"agents",
"engineering",
"workflow",
"rigor"
]
}
What it installs
The manifest is a name and a version. 32 skills, 4 agents, 1 hook travel with it, and installing the plugin installs all of them — 3,149 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill help A 61 tokens
- Skill interview A 143 tokens
- Skill init A 55 tokens
- Skill converge A 113 tokens
- Skill deprecate A 97 tokens
- Skill lint A 90 tokens
- Skill analyze A 98 tokens
- Skill constitution A 98 tokens
- Skill explain A 59 tokens
- Skill roadmap A 88 tokens
- Skill breakdown A 92 tokens
- Skill checklist A 128 tokens
- Skill qa A 66 tokens
- Skill debug A 63 tokens
- Skill prompt A 76 tokens
- Skill blueprint A 98 tokens
- Skill clarify A 108 tokens
- Skill deepen A 108 tokens
- Skill double-check A 129 tokens
- Skill levelup A 72 tokens
- Skill living-docs A 116 tokens
- Skill persona A 84 tokens
- Skill route A 50 tokens
- Skill signature A 71 tokens
- Skill specify A 108 tokens
- Skill assess A 108 tokens
- Skill handoff A 79 tokens
- Skill learn A 65 tokens
- Skill performance A 57 tokens
- Skill prototype A 50 tokens
- Skill report A 80 tokens
- Skill quarantine C 121 tokens
- Agent code-reviewer A 75 tokens
- Agent tech-scout A 90 tokens
- Agent refactorer A 86 tokens
- Agent architect A 67 tokens
- Hook SessionStart A not measured
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 14d ago Changed 799b297acf5c
- 15d ago Changed bc7c50ee9654
- 1mo ago First seen · 21 lines scan A e025b8d9e16b
mastermind is a plugin published in the GitHub repository mehrad-dm/mastermind (23 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
nxtg-forge
Governance-native AI development — 33 agents, 24 commands, 27 skills, 27 hooks (4 blocking security guards, an opt-in enforced-task test guard and Stop gate, a Stop check on required command output, and Semgrep scanning), drift detection (needs a configured model), an optional CRUCIBLE test-review prompt, and shared…
god-prompt-mcp
GodPrompt engineering workflows for task routing, TDD, debugging, verification, and progressive disclosure.
minimalist
Subtraction-first engineering for AI agents. The smallest correct change wins.
prompt-engineering-expert
Designing effective prompts: structure, few-shot, chain-of-thought, output formatting, and evaluation.
macos-notch
Design and implement macOS Dynamic Island / notch-style apps — NSPanel, geometry, state machine, module widgets (media, HUD, shelf, agents).
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.