mastermind-frontend-audit

mastermind-frontend-audit is a skill for Claude Code, Codex from xcrft/mastermind. It costs 76 tokens per session (1,339 once invoked), scanned A, original, MIT.

A read-only review skill for checking whether React or Vue interface changes are correctly connected to the rest of the codebase and follow its design system.

In plain words
What is it for?
Use it after a React or Vue change to check component usage, caller contracts, reuse of existing components, and design-system tokens.
Why use it?
A screen can look correct while its component is never rendered, its props no longer match callers, or it duplicates an existing component.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/xcrft/mastermind/mastermind-frontend-audit
Any agent
npx skills add xcrft/mastermind --skill mastermind-frontend-audit
Clone the repo
git clone --depth 1 https://github.com/xcrft/mastermind

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for mastermind-frontend-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/xcrft/mastermind/mastermind-frontend-audit.svg)](https://agentmods.dev/skills/xcrft/mastermind/mastermind-frontend-audit)
Your own site
<a href="https://agentmods.dev/skills/xcrft/mastermind/mastermind-frontend-audit"><img src="https://agentmods.dev/badge/skills/xcrft/mastermind/mastermind-frontend-audit.svg" alt="Measured on agentmods" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,339 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00076 $0.01339
Opus 5 $0.00038 $0.00669
Sonnet 5 $0.00015 $0.00268
Haiku 4.5 $0.00008 $0.00134

Measured 5d ago against content hash 7d2530819439, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

mastermind-frontend-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 5d 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.

skills/code-review/mastermind-frontend-audit/SKILL.md · 150 lines

How it starts

The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Mastermind frontend audit

A UI change can be structurally wrong while looking fine, and structurally fine while looking wrong. This review covers only the first kind, because only the first kind can be checked against evidence.

You are read-only. You report findings and change nothing.

Collect the delta first

git diff --name-status <baseline>
git diff <baseline> -- <changed component files>

Then ground each changed component in the graph. Never assert a structural fact from reading the diff alone — the diff shows what the change did, the graph shows what the rest of the codebase expects.

The four checks

1. A component nothing renders

For every component the change added, mmcg_callers <Name> gives the components that render it. Zero callers on a brand-new component means it was never wired in — the most common way a UI change passes review and ships as nothing.

Do not report this as dead code. Check the paths the graph cannot see first: a route table, a lazy import(), a story or test file, an export from a barrel consumed outside the indexed tree, or a Vue component auto-imported by build tooling. If one of those explains it, the finding is could_not_verify, not a defect.

2. A props contract changed without its callers

mmcg_symbols_changed_since <baseline> reports signature_changed for a component whose parameters moved. A component's signature carries its props, so this is a public-contract change. Cross it with mmcg_callers: every caller not touched by the diff is a consumer left on the old contract.

A removed or newly-required prop breaks them. An added optional prop does not. Say which, and name the callers — a count is not evidence.

3. A reinvented component

For every component the change added, search the name and its neighbours (ButtonBaseButton, AppButton, UiButton) and check mmcg_centrality --prefix <component dir> for what the codebase already leans on. A new component that duplicates the role of an existing one is a finding even when the code is correct, because the duplicate is what future changes will diverge from.

Read the full file on GitHub · 150 lines

Files

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.

Changes

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.

  1. 5d ago First seen · 150 lines · 76 tokens per session scan A 7d2530819439

Subscribe to this mod's changes

mastermind-frontend-audit is a skill published in the GitHub repository xcrft/mastermind (11 stars, last pushed 5d ago), licensed MIT. It adds 76 tokens to every session and 1,339 once invoked, about $0.0004 per session on Opus 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.

Related

Other skills, from other repositories

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…

Cranot/roam-code · 86 tokens

orchestrate

Tree-aware multi-agent GitHub-issue pool. Conductor manages task-tree from task-splitting-evaluation, executing depth-first per branch while parallelizing roots/orphans. Each worker agent owns its subtree lifecycle. Conductor tracks state (pending/started/in-progress/completed/halted) in GitHub +…

MercurieVV/ScalaSemantic · 101 tokens

bonsai-ninja

Use bonsai-ninja as compiler-backed structural evidence when mapping a codebase, finding symbols, tracing behavior, inspecting dataflow, debugging across files, reviewing change impact, exporting graph facts, or running SAST.

gromhacks/bonsai-ninja · 48 tokens

task-splitting-evaluation

Recursive pre-implementation GitHub task splitting and evaluation flow. Use when the user wants Claude agents to evaluate unhandled tasks, skip already-processed tasks, mark easy leaves with detailed executor-ready comments, split broad tasks into GitHub subtasks, and keep recursing until every leaf is well described…

MercurieVV/ScalaSemantic · 73 tokens

gh-task

Run a GitHub issue end-to-end in this repository using the committed isolated-worktree workflow. Use when the user invokes $gh-task, asks to run a GitHub task, or provides a GitHub issue number.

MercurieVV/ScalaSemantic · 47 tokens

stacklit-navigator

Use stacklit.json to navigate codebases without burning tokens on file exploration.

glincker/stacklit · 19 tokens