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/monoes/monomindWrote 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/monoes/monomind/improve)<a href="https://agentmods.dev/commands/monoes/monomind/improve"><img src="https://agentmods.dev/badge/commands/monoes/monomind/improve/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/monoes/monomind/improve"><img src="https://agentmods.dev/badge/commands/monoes/monomind/improve.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.00026 | $0.03702 |
| Opus 5.5 | $0.00010 | $0.01481 |
| Sonnet 5.5 | $0.00005 | $0.00740 |
| Haiku 4.5 | $0.00003 | $0.00370 |
Grade A, and why
improve 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 yesterday.
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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First — extract repeat flags: Follow the REPEAT PREAMBLE from mastermind-repeat/SKILL.md. Extracts --repeat, --tillend, --maxruns, --wait, --rep, --loop from $ARGUMENTS before all other parsing. If is_continuation = true, skip the empty-arguments check below.
If $ARGUMENTS is empty, output this and STOP:
Usage:
/mastermind:improve <component or concept>Examples:
/mastermind:improve the authentication flow/mastermind:improve error handling across the codebase/mastermind:improve CLI startup performance/mastermind:improve the MCP server architectureBy default, analysis is saved to
docs/improvements/YYYY-MM-DD-<slug>.md. Add--monotaskto write to a monotask board instead.
Do NOT proceed further if no arguments were provided.
Extract --monotask flag: If present, set USE_MONOTASK=true and remove from $ARGUMENTS. Default: USE_MONOTASK=false.
Step 0: Check monotask CLI (skip unless --monotask was passed)
Only run this step if USE_MONOTASK=true.
command -v monotask || (command -v cargo && cargo install monotask)
If neither exists, tell user to install Rust + monotask and STOP.
Step 1: Gather Project Context
Collect ALL of the following in parallel (skip any that error):
-
Repo name: Run
git remote get-url origin, extract the last path segment, strip.git. Fallback:basenameof the current working directory. Store asREPO_NAME. -
README: Read
README.md(first 200 lines). Skip if missing. -
Package manifest: Read whichever exists first:
package.json,Cargo.toml,pyproject.toml,go.mod. Extract name, description, and keywords/tags. -
Knowledge graph: Call
mcp__monomind__monograph_suggestwith the user's prompt ($ARGUMENTS). Skip if it errors or returns empty. -
Memory search: Call
mcp__monomind__memory_pattern-searchwith the user's prompt ($ARGUMENTS). Use the top 5 results.
Bundle all gathered information into a single PROJECT_CONTEXT string for downstream agents.
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.
- yesterday First seen · 345 lines · 26 tokens per session scan A bb01226dab96
improve is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 3,702 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-10-26.
Other commands, from other repositories
doctor
Health-check the harness: kernel load, MCP wiring, memory backend, host adapter.
review-diff
Review the current working diff for correctness, security, and reuse.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
prp-plan
Create comprehensive feature implementation plan with codebase analysis and pattern extraction.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.
checklist
Generate a custom checklist for the current feature based on user requirements.