mastermind-project-map

A repository-exploration workflow that builds an evidence-backed map of a codebase: its entry points, central symbols, components, dependency cycles, and hotspots. A codegraph is an indexed view of how files and symbols relate.

In plain words
What is it for?
Use it to plan where to read first, understand architecture, find important components, inspect dependency cycles, and explain which parts of the repository the map covers.
Why use it?
It gives you a reliable starting point in an unfamiliar repository instead of guessing from filenames. It also reports when the map is incomplete or truncated.

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-project-map
Any agent
npx skills add xcrft/mastermind --skill mastermind-project-map
Clone the repo
git clone --depth 1 https://github.com/xcrft/mastermind

Made for: Claude Code, Codex.

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 588 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 $0.00057 $0.00588
Opus 5 $0.00028 $0.00294
Sonnet 5 $0.00011 $0.00118
Haiku 4.5 $0.00006 $0.00059

Measured 2d ago against content hash 2e0bc7a781c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mastermind-project-map 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 2d 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/workflow/mastermind-project-map/SKILL.md · 64 lines

How it starts

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

Mastermind Project Map

Use the deterministic map as the source of claims. Do not reconstruct a map from filenames or model intuition when the backend is available.

Workflow

  1. Confirm the repository has a fresh index with mastermind status. If it is absent or stale and the request permits local indexing, run mastermind index . before mapping.

  2. Choose the narrowest useful repository-relative scope. Use . only for a repository-wide briefing.

  3. Run JSON first:

    mastermind map PATH --format json --depth 2 --top 20
    

    Add --production-only for architecture work where tests, fixtures, examples, generated output, vendored code, and dependency trees would otherwise dominate the briefing. With MCP, pass production_only: true.

    Use mmcg_map instead when MCP is the active interface. Treat both as the same schema-v1 engine.

  4. Check scope, every collection's truncated/truncation_reason, limits, and precision_notes before interpreting results.

  5. Produce a reading order: entry points first, then central symbols, component boundaries, and cycles. Cite repository-relative files and symbol lines.

Treat directory-derived components as navigation groups, not proven semantic subsystems. Prefer the explicit production filter over manually ignoring fixture/example/generated results. Keep those paths when the user is asking about tests, examples, or packaging. De-prioritize high-collision symbol names. A top_probe proves only that more rows exist; do not imply the backend can return an uncapped full list. Narrow the path or change top within its supported range instead.

Use text for a compact terminal briefing and Mermaid only when the user asks for a diagram. Do not infer runtime entry points from a heuristic label.

Reporting contract

Separate:

  • indexed facts: languages, files, symbols, callers, cycles;
  • heuristics: filename entry points;
  • approximations: syntactic edges, name collisions, work-limit skips.

Read the full file on GitHub · 64 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. 2d ago First seen · 64 lines · 57 tokens per session scan A 2e0bc7a781c6

Subscribe to this mod's changes

mastermind-project-map is a skill published in the GitHub repository xcrft/mastermind (11 stars, last pushed 7d ago), licensed MIT. It adds 57 tokens to every session and 588 once invoked, about $0.0003 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