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 skills add mehrad-dm/mastermind --skill reportgit 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/skills/mehrad-dm/mastermind/report)<a href="https://agentmods.dev/skills/mehrad-dm/mastermind/report"><img src="https://agentmods.dev/badge/skills/mehrad-dm/mastermind/report/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/skills/mehrad-dm/mastermind/report"><img src="https://agentmods.dev/badge/skills/mehrad-dm/mastermind/report.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.00080 | $0.00714 |
| Opus 5.5 | $0.00032 | $0.00286 |
| Sonnet 5.5 | $0.00016 | $0.00143 |
| Haiku 4.5 | $0.00008 | $0.00071 |
Grade A, and why
report 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
report: a receipt for the work
Turn a completed cycle into a concise, skimmable record someone can read without re-reading the diff. It's the same content as the in-chat verdict, made durable and shareable.
When it runs
- On request: "give me a report", "write up what you did", "summarize this cycle".
- Automatically at the end of
build/qaonly if the project preference says so (below). Default is off: otherwise the in-chat verdict is the whole deliverable.
Preference (per project): off by default
Read .mastermind/prefs.md in the project root for a cycle-report: line: one of:
off(default, and the assumption if the file/key is missing): report only on explicit request.ask: at the end of a report-worthy cycle, offer once: "want a report? markdown / html / no".markdown: always write a Markdown report.html: always write a self-contained HTML report.
The init skill sets this once, at the first task. The user can change it anytime ("reports off",
"always give me html reports"): update the line in .mastermind/prefs.md to match.
What goes in it: signal, not a log
- Title + verdict: Done · Done, not fully checked · Not done · Wrong thing, one line why,
and the
not checked:line. - What changed: files touched (path + one-line what), grouped by area.
- Key decisions: the non-obvious calls and the one-line reason (not what the model already knows).
- How it was verified: what was actually run/observed end-to-end, and what it produced.
- Follow-ups / risks: anything left, edge cases, TODOs.
Keep it tight: a bloated report gets ignored (same rule as the brain: signal density beats volume).
Format
- Markdown (default): write
.mastermind/reports/<slug>-<YYYY-MM-DD>.md(use today's date), or a path the user names. Cheap, diffable, opens anywhere. - HTML (on request /
cycle-report: html): one self-contained file (inline CSS, no external assets or scripts), lightly MasterMind-styled, so it opens in any browser. Costs more tokens.
What ships with it
1 file beside SKILL.md 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.
- 15d ago Changed · +80 tokens per session f6ded226a794
- 1mo ago First seen · 54 lines · 0 tokens per session scan A 6381921c05a3
report is a skill published in the GitHub repository mehrad-dm/mastermind (23 stars, last pushed 6d ago), licensed MIT. It adds 80 tokens to every session and 714 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 skills, from other repositories
st-full-workflow
Use when the user asks to run the complete end-to-end Strikethroo workflow for a work order in one shot in this repository — triggers include full workflow, end-to-end, plan and execute, do everything, run the whole strikethroo workflow. Do not use when the user wants only one stage (create a plan, generate tasks, or…
code-sec-review
Static security review that hunts exploitable vulnerabilities, prioritizing unauthenticated and cross-tenant attack paths.
agent-decision
Deterministic self-evaluation rubric for decision escalations — scored every run using the FRAME framework.
code-quality-review
Reviews code and plans against the project's coding rules.
review-loop
Two-mode review loop — single reviewer per epic, three reviewers for full branch.
setup-new-acpx-key
Configure the API key (or other credential) for a registered ACPX agentid (claude/codex/cursor/gemini/qwen/copilot/pi/droid/iflow/kilocode/kimi/kiro/opencode/tlamatini) end-to-end across data.keys, config.json (top-level + acpx.agents. .env), regensecrets.py, and verification via acpdoctor.