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/examples)<a href="https://agentmods.dev/commands/monoes/monomind/examples"><img src="https://agentmods.dev/badge/commands/monoes/monomind/examples/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/examples"><img src="https://agentmods.dev/badge/commands/monoes/monomind/examples.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.00030 | $0.01185 |
| Opus 5.5 | $0.00012 | $0.00474 |
| Sonnet 5.5 | $0.00006 | $0.00237 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
pair:examples 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pair Programming Examples
Real-world scenarios with actual Claude Code patterns — no fictional CLI.
Example 1: Feature Implementation (Navigator Mode)
Goal: Implement JWT authentication with refresh tokens.
Setup:
npx monomind hooks pre-task -d "Implement JWT auth with refresh tokens"
Session:
"Implement JWT auth middleware for Express. Include: access token (15min expiry), refresh token (7 days), token rotation on refresh, and blacklisting revoked tokens. Start with the token generation utilities, then we'll do the middleware."
Claude implements. Review each piece:
"Good. One issue: store refresh tokens in Redis, not in-memory. Update that before continuing."
After middleware is done:
"Now write unit tests for the token generation utilities. Use Jest. Cover: valid tokens, expired tokens, tampered tokens, and token rotation."
End:
"Summarize what we built and what's still needed before this is production-ready."
npx monomind hooks post-task --task-id <id> --success true
Example 2: Debugging (Debug Mode)
Goal: Memory leak in a Node.js service.
Setup:
Skill("mastermind-debug")
Or directly:
"Debug session: our Node.js service leaks memory — grows from 150MB to 450MB over 10 minutes, then crashes. I'll share code as needed. Start by asking me questions to narrow down the cause."
Claude asks targeted questions. You share relevant code sections.
"Here's the event emitter setup: [paste code]"
"Found it: EventEmitter listeners aren't removed on cleanup. Show me the fix and explain why this pattern causes the leak."
Apply the fix, verify:
"Fixed. Write a test that would have caught this — one that monitors memory over time or checks listener counts."
Example 3: TDD (TDD Mode)
Goal: Shopping cart feature, test-first.
Setup:
Skill("mastermind-debug") # Phase 4: failing test first, then Red-Green-Refactor
Or:
"TDD session: shopping cart. Write failing tests first for: add item, remove item, update quantity, calculate total, apply discount. Then I'll implement each. Don't write implementation code — just tests."
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 · 157 lines · 30 tokens per session scan A 70d78d813d82
pair:examples is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 30 tokens to every session and 1,185 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
test
Design or run focused test validation for a task, bug, or diff.
build-fix
Systematically investigate and fix build errors, TypeScript errors, or test failures with minimal diffs.
verify
Run verification loop to validate implementation.
tdd
Test-driven development with TodoWrite planning and comprehensive testing.
self-healing
Automatically detect and recover from errors without interrupting your flow.
checklist
Generate a custom checklist for the current feature based on user requirements.