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 xcrft/mastermind --skill mastermind-project-historygit clone --depth 1 https://github.com/xcrft/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/xcrft/mastermind/mastermind-project-history)<a href="https://agentmods.dev/skills/xcrft/mastermind/mastermind-project-history"><img src="https://agentmods.dev/badge/skills/xcrft/mastermind/mastermind-project-history/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/xcrft/mastermind/mastermind-project-history"><img src="https://agentmods.dev/badge/skills/xcrft/mastermind/mastermind-project-history.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00079 | $0.01611 |
| Opus 5.5 | $0.00032 | $0.00644 |
| Sonnet 5.5 | $0.00016 | $0.00322 |
| Haiku 4.5 | $0.00008 | $0.00161 |
Grade A, and why
mastermind-project-history 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 1mo 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mastermind Project History
Recover decision context without inventing institutional memory. Markdown
artifacts are authoritative; mmcg_history is a rebuildable retrieval index.
Sources
The history corpus admits only:
CONTEXT.md- root-level
CONTEXT-archive-*.md .mastermind/tasks/<task>/spec.md.mastermind/tasks/<task>/executor-report.md.mastermind/tasks/<task>/audit.md.mastermind/releases/<name>.md- legacy
.mastermind/tasks/<task>/release-notes.md .mastermind/tasks/_lessons.md- Markdown files, including nested directories, under
docs/adr/,docs/adrs/,docs/decisions/,adr/,adrs/, or.mastermind/decisions/(kind: architecture_decision)
Arbitrary scratch files are not history. Git history and current runtime code may contradict or supersede a record, so inspect them when the answer is load-bearing.
Workflow
- Query
mmcg_historywith the narrowest useful terms and optionalkind. If the caller supplies a saved document graph, pass its path asdocument_graphso the history retrieval and live graph check share one response without importing the graph into SQLite. Readfreshness_errorbefore interpreting an empty result:unknownmeans the live corpus was not checked, whileincompletemeans a known admission or work limit omitted evidence. Resolve the reported root or scan error before treating absence as evidence. - Read the returned Markdown around each relevant match. Search rank is not confidence, and co-occurrence is not causality.
- Resolve explicit status and supersession links. An accepted or active record
can constrain the plan; a proposed record remains a proposal. Follow
Supersedeslinks in both directions and inspect the replacement's status. A newer date or filename alone does not replace an accepted decision. If status is absent or records conflict, say so. A lesson with statuscandidateis an audit signal awaiting semantic review, not active guidance and not proof of a reusable root cause. - Preserve negative history: a relevant rejected alternative, failed attempt, audit defect, or gotcha must constrain the new plan unless new evidence directly addresses its failure mode.
- Verify technical claims against current code, tests, or runtime evidence. Provenance answers "where did this claim come from?"; it does not answer "is this claim true?" User approval proves authorization, not correctness.
- If evidence is thin for a security, runtime-boundary, migration, money,
idempotency, or compatibility conclusion, return
insufficient evidenceand name the missing proof.
What ships with it
3 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.
- 1mo ago Changed · +4 lines 88c7c8c8ee08
- 1mo ago Changed · +31 lines f6295cd288a1
- 1mo ago Changed · +29 lines · +12 tokens per session 5caa8f746ba0
- 1mo ago First seen · 90 lines · 67 tokens per session scan A 8468497fb5fe
mastermind-project-history is a skill published in the GitHub repository xcrft/mastermind (13 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 1,611 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
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
knowledge-meeting-ingest
Ingest meeting transcripts from any recorder into Knowledge with attendee enrichment, timeline merge, supported decisions and commitments, and verification of substance and sequence. Summary-only input is not a verified meeting ingestion.
knowledge-automation
Create scheduled Knowledge ingestion automations with a verified worker, private-vault authority, and an end-to-end scheduled run. Use when asked to schedule or repair recurring ingestion from any source.
knowledge-base
Create and maintain a Markdown knowledge base that any AI agent can read, search, and update. Use when the user wants to start a knowledge base, add or update notes, organize docs/notes for an agent or LLM to consume, build an index of notes, or run a cleanup/maintenance pass on an existing MD knowledge base. Triggers…
obsidian-vault
Organize Obsidian vaults with MOCs, wikilinks, frontmatter/properties, dashboards, orphan-note checks, and cleanup workflows. Use ONLY when the user explicitly refers to Obsidian — by naming "Obsidian", an Obsidian "vault", or an Obsidian-specific feature such as wikilinks ("[[ ]]"), the Dataview or Bases plugins, or…
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…