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 agentmods add skills/xcrft/mastermind/mastermind-cross-client-setupnpx skills add xcrft/mastermind --skill mastermind-cross-client-setupgit 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-cross-client-setup)<a href="https://agentmods.dev/skills/xcrft/mastermind/mastermind-cross-client-setup"><img src="https://agentmods.dev/badge/skills/xcrft/mastermind/mastermind-cross-client-setup.svg" alt="Measured on agentmods" 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 | $0.00079 | $0.00509 |
| Opus 5 | $0.00039 | $0.00254 |
| Sonnet 5 | $0.00016 | $0.00102 |
| Haiku 4.5 | $0.00008 | $0.00051 |
Grade A, and why
mastermind-cross-client-setup 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 3d 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.
What it actually says
Mastermind Cross-Client Setup
Use the built-in adapter. Do not hand-edit client configuration unless the adapter reports an unsupported case.
Workflow
-
Separate the workflow bundle from MCP registration. For Claude or Codex workflow skills, use
mastermind install --client CLIENT; use--client allfor both. Claude also receives spawnable subagents. Verify installed ownership and SHA-256 content parity withmastermind doctor --workflow --client CLIENT. -
Resolve MCP client and scope from the request. Respect the capability matrix: Codex is user-scope only; Generic requires an explicit config path; Continue owns its standalone Mastermind YAML file.
-
Run an MCP dry-run first:
mastermind setup CLIENT --scope SCOPE --root . [--config PATH] -
Explain only the redacted action summary. Never print existing config, environment values, unknown fields, or subprocess output.
-
If the user authorized installation/update/removal and the preview matches, repeat with
--write. Add--removeonly for removal. -
Use
--forceonly after explicitly showing that a customized Mastermind entry will be backed up and replaced/removed. Never use force to imply write. -
Run
mastermind doctor ROOT, using the same root passed to setup, and report structural config status separately from the trusted current-binary MCP handshake. On a new project without.mastermind/mmcg.db, explain that the config can be canonical while the overall doctor exits nonzero and skips the handshake; index the project before requiring an all-green doctor.
Preserve unrelated servers/settings. Stop on malformed/duplicate configs, symlinks, concurrent edits, unsupported scope, missing native CLI, or unsafe path resolution. Do not execute the command stored in client configuration.
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.
- 3d ago First seen · 46 lines · 79 tokens per session scan A b38b62316041
mastermind-cross-client-setup is a skill published in the GitHub repository xcrft/mastermind (11 stars, last pushed 9d ago), licensed MIT. It adds 79 tokens to every session and 509 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.
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…
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 +…
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.
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…
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.
stacklit-navigator
Use stacklit.json to navigate codebases without burning tokens on file exploration.