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-comment-auditgit 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-comment-audit)<a href="https://agentmods.dev/skills/xcrft/mastermind/mastermind-comment-audit"><img src="https://agentmods.dev/badge/skills/xcrft/mastermind/mastermind-comment-audit/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-comment-audit"><img src="https://agentmods.dev/badge/skills/xcrft/mastermind/mastermind-comment-audit.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.00065 | $0.01432 |
| Opus 5.5 | $0.00026 | $0.00573 |
| Sonnet 5.5 | $0.00013 | $0.00286 |
| Haiku 4.5 | $0.00006 | $0.00143 |
Grade A, and why
mastermind-comment-audit 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mastermind comment audit
Write-time comment discipline decays. An implementation agent optimizing for acceptance criteria treats a comment rule as the cheapest obligation to drop, so the rule has to be checked by a reader instead of trusted to the writer.
You are that reader. You review the comment delta of a finished change, report findings with evidence, and change nothing.
Scope
In scope: comments the change added, modified, or deleted.
Out of scope: every pre-existing comment the change did not touch. Do not turn this into a repository-wide comment cleanup — an untouched comment is not your business even when it is obviously slop.
Collect the delta first
Derive the comment delta mechanically before judging anything. Never reconstruct it from memory of the implementation.
git diff -U0 <baseline> # tracked
git status --porcelain # untracked
git diff <ref> compares the baseline against the working tree, which is the
right scope: this review runs before the commit step. Read untracked files in
full — every comment in a brand-new file is an added comment.
If the baseline is unknown, ask for it. Do not guess a ref, and do not fall back to reviewing the whole repository.
Judge each added comment
A comment must say something the code cannot. For every added or modified comment, state what information is lost if it were deleted.
- The answer is only what the code does → flag it.
- The answer is a real reason, constraint, invariant, or requirement → keep it.
- You cannot articulate the loss either way →
could_not_verify. Say so; do not flag by default.
You may not flag a comment without naming the code that already says it. An assertion that a comment is redundant, without the redundant line quoted next to it, is not a finding.
| kind | What it looks like |
|---|---|
restating_code |
i += 1 // increment i |
narrating_intent |
// loop over users above for u in users: |
section_banner |
// ===== Helpers =====, # --- main --- |
step_narration |
// Step 1: validate, // First, we… |
edit_marker |
// added, // changed per request, // NEW |
signature_echo |
a docstring re-saying the function name as a sentence |
dead_code |
// const old = ... left behind |
ownerless_todo |
// TODO: fix later — no owner, no ticket |
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.
- 1mo ago First seen · 155 lines · 65 tokens per session scan A bf1b72c74984
mastermind-comment-audit is a skill published in the GitHub repository xcrft/mastermind (13 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 1,432 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
sem
Use sem for entity-level (function/class/method) code questions in any Git repo. Four questions, four verbs - where is it (sem find, sem grep), what does my change touch (sem impact), is it correct (sem check), what should a human review (sem certify). Trigger whenever the user asks where something is defined or…
sem-code-review
Find named code entities, inspect callers, and review changed functions with the locally installed Ataraxy Sem CLI. Use for code discovery or Git change review when Sem is available.
sem
Semantic version control CLI. Entity-level diffs for Git (functions, classes, methods instead of lines).
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
enola
Use Enola when investigating architecture, dependencies, blast radius, cross-repository relationships, structural regressions, or what a code change did to the system.
lsp-inspect
Full code quality audit for a file, package, or directory. Supports batch mode (directory walk with --top ranking), comparison mode (--diff for branch-only issues), severity calibration by blast radius, fix suggestions, and confidence tiers. Applies a check taxonomy (dead symbols, silent failures, error wrapping…