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 checklistgit 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/checklist)<a href="https://agentmods.dev/skills/mehrad-dm/mastermind/checklist"><img src="https://agentmods.dev/badge/skills/mehrad-dm/mastermind/checklist/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/checklist"><img src="https://agentmods.dev/badge/skills/mehrad-dm/mastermind/checklist.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.00128 | $0.00844 |
| Opus 5.5 | $0.00051 | $0.00338 |
| Sonnet 5.5 | $0.00026 | $0.00169 |
| Haiku 4.5 | $0.00013 | $0.00084 |
Grade A, and why
checklist 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MasterMind: Checklist
A checklist here is a unit test for the requirements' wording: each item asks whether the spec says enough, clearly enough, about one concern. It never asks whether the code works. Feature and concern: $ARGUMENTS.
Tests the code (wrong here): Verify the logo shows on the home page.
Tests the requirement (right): Does the spec say what is shown when the logo fails to load? [Gap, Edge cases]
Write it
- Pick the concern. From the request, or the riskiest one the spec touches: security, privacy, UX, accessibility, API, data, performance, localization. Ask only if two concerns are equally likely, and recommend one.
- Read the feature's
spec.md, plusplan.mdandtasks.mdif they exist, and the constitution. - Write 10 to 30 items to
specs/<feature>/checklists/<concern>.md. Each item is a question about the requirements, ends with its quality dimension, and cites a spec ID or[Gap]:
- [ ] CHK007 Are rate limits specified for every public endpoint? [Completeness, FR-009]
- [ ] CHK008 Is "secure session" defined with an expiry and a revocation rule? [Clarity, FR-012]
- [ ] CHK009 Does the spec say who may delete another user's export? [Gap, Coverage]
When a model's output drives an action, the security list asks whether the spec limits that action in code. An instruction in a prompt is not a boundary.
Quality dimensions: Completeness · Clarity · Consistency · Measurability · Coverage (edge, error, recovery, non-functional) · Assumptions · Conflicts.
Rules
- At least 80% of items cite a spec ID or
[Gap]. An item with no anchor is an opinion. - Never tick a box you generated.
[x]means a reviewer judged the requirement good enough. Mark only what the user asks you to evaluate, and say which you marked. - Append, never overwrite. A second run on the same concern adds items with new IDs.
- Items start with a question word: Are, Is, Does, Do, Can. "Verify", "Test" and "Confirm" mean you slipped into testing code.
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 First seen · 60 lines · 128 tokens per session scan A 16a93b0fdf47
checklist is a skill published in the GitHub repository mehrad-dm/mastermind (23 stars, last pushed 6d ago), licensed MIT. It adds 128 tokens to every session and 844 once invoked, about $0.0005 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-10-08.
Other skills, from other repositories
test-fix
Diagnose and minimally fix a failing test, then re-run.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code. Enforces red-green-refactor cycle with strict rules.
browser-inspect
Browser inspection and interaction for verifying rendered web UI during development.
review
Review current code changes for bugs, regressions, test gaps, and project-guideline violations.
coder-self-review
Deterministic self-evaluation rubric for Coder — scored every run using the GRASP framework.
hatch3r-browser-verify
Opt-in browser verification skill — spec-run-first Playwright verification (assertions execute in the runner, agent reads only failures), axe-core a11y audits, toHaveScreenshot() regression diffs, E2E test scaffolds, and snapshot-mode exploratory driving. Default ON for UI-affecting agent invocations; disable globally…