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.
git clone --depth 1 https://github.com/alexmond/alexmskillsWrote 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/commands/alexmond/alexmskills/compile)<a href="https://agentmods.dev/commands/alexmond/alexmskills/compile"><img src="https://agentmods.dev/badge/commands/alexmond/alexmskills/compile/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/commands/alexmond/alexmskills/compile"><img src="https://agentmods.dev/badge/commands/alexmond/alexmskills/compile.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00013 | $0.00297 |
| Opus 5.5 | $0.00005 | $0.00119 |
| Sonnet 5.5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
compile 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.
What it actually says
/mindmap-prompt:compile
Turn a .canvas map into an organized Markdown prompt — then do the work it
describes. The compiled prompt is the user's actual request, not a report to
hand back.
What to do
-
Pick the map: the name in
$ARGUMENTS, else the only file in.claude/mindmap/, else ask which one. -
Compile it:
python3 <plugin>/scripts/mindmap.py compile .claude/mindmap/<name>.canvas -
Read the output and treat it as the prompt. Plan and execute it the way you would any request of that size.
-
Surface any warnings in one line first — especially "not connected to the goal", because that is content the user wrote that did not reach the prompt. Offer
--include-orphansif it looks unintentional. -
If compilation fails, show the errors plainly (usually: no
#goalnode, or more than one) and offer to reopen the canvas.
Flags
--include-orphans— keep unconnected nodes under## Unsorted notes.-o <file>— write the prompt to a file instead of stdout.
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 · 33 lines · 13 tokens per session scan A ca3cf0b0725d
compile is a command published in the GitHub repository alexmond/alexmskills (9 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 297 once invoked, about $0.0001 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-31.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
discuss
A command that interviews you in five phases and saves a detailed description of a proposed feature or change. EARS is a structured way to write requirements so they can be checked clearly.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
rev
Invoke Code Reviewer for code quality, security, requirements validation, and best practices review.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.