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 constitutiongit 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/constitution)<a href="https://agentmods.dev/skills/mehrad-dm/mastermind/constitution"><img src="https://agentmods.dev/badge/skills/mehrad-dm/mastermind/constitution/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/constitution"><img src="https://agentmods.dev/badge/skills/mehrad-dm/mastermind/constitution.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.00098 | $0.01192 |
| Opus 5.5 | $0.00039 | $0.00477 |
| Sonnet 5.5 | $0.00020 | $0.00238 |
| Haiku 4.5 | $0.00010 | $0.00119 |
Grade A, and why
constitution 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MasterMind: Constitution
A constitution is the short list of rules this project refuses to break, written so a reviewer can
check a change against each one. It outranks every spec, plan and task (~/.mastermind/engineering/core/spec-driven.md).
Request: $ARGUMENTS.
Write it
- Read what the project already says. README, CI config, lint and type settings,
.mastermind/brief.md, existingspecs/. Rules the repo already enforces are facts to record, not questions to ask. - Start from the template. Use
specs/.templates/constitution.mdif it exists, elsetemplate.mdbeside this file. Write tospecs/constitution.md. - Draft at most seven principles. One is enough when the project has one rule. Each is a name, a few
MUSTorMUST NOTstatements, and one line of rationale. More than seven means some are preferences. - Ask only for what the repo cannot tell you. One question at a time, each with your recommended
answer (
interview). Privacy stance, compliance, and what the product will never do are the usual ones. - Leave no placeholder behind. A value nobody knows yet stays as
TODO(<what>): <why it is unknown>and is listed in your report.
Amend it
- Version every change in the footer line, semver:
- MAJOR: a principle is removed or redefined so that old work may now violate it.
- MINOR: a principle or section is added, or its guidance materially changes without making old work non-compliant, which includes narrowing an obligation.
- PATCH: wording, typos, clarifications that change no obligation.
- Record the amendment as a comment block at the top of the file: the version change, what changed and why, the date, and who decided it.
- Ripple the change. List every living doc, open spec, plan and template that now conflicts with the new rule. Update each one, or name it in the comment block as pending, with the reason.
Write rules a reviewer can check
Weak: Code should be well tested.
Strong: Money arithmetic MUST have a failing test written before the code that makes it pass.
Rationale: rounding bugs in payouts are invisible until a customer finds them.
Ratchet: Test coverage of src/billing MUST NOT fall below 81.4% (measured 2026-10-07 by `npm run cov`).
Rationale: we cannot reach 100% today, and we refuse to get worse.
What ships with it
2 files 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 · 78 lines · 98 tokens per session scan A 398bf87208f2
constitution is a skill published in the GitHub repository mehrad-dm/mastermind (23 stars, last pushed 6d ago), licensed MIT. It adds 98 tokens to every session and 1,192 once invoked, about $0.0004 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
st-execute-blueprint
Use when the user asks to run, execute, implement, or carry out a Strikethroo plan or its blueprint by plan ID in this repository — triggers include execute blueprint, run the plan, implement plan, build the plan. Do not use to create a plan, to only generate tasks, to run a single task, or for generic development…
st-generate-tasks
Use when the user asks to decompose, break down, or generate tasks for an existing Strikethroo plan ID in this repository — triggers include generate tasks, break down the plan, decompose plan, create the task blueprint. Do not use to create a new plan, to execute tasks, or for generic project planning outside…
st-create-plan
Use when the user asks to draft, scope, or write up a new Strikethroo plan for a work order, feature, or initiative in this repository — triggers include create plan, new plan, plan this, scope a plan, strikethroo plan. Do not use to decompose an existing plan into tasks, to execute a plan, or for generic…
plan-management
Plan lifecycle — grill entry point, grounding, artifact review, per-epic execution, revision.
architect-impl-grounding
Grounds the grill's settled decisions in the codebase — annotates impl.md with file paths, signatures, reference files, test specs, and LOC; re-grounds the next epic after each landing.
task-tracking
File-based to-do tracking for multi-step and multi-session work.