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/session)<a href="https://agentmods.dev/commands/monoes/monomind/session"><img src="https://agentmods.dev/badge/commands/monoes/monomind/session/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/session"><img src="https://agentmods.dev/badge/commands/monoes/monomind/session.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.00033 | $0.00835 |
| Opus 5.5 | $0.00013 | $0.00334 |
| Sonnet 5.5 | $0.00007 | $0.00167 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
pair:session 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pair Programming Session Lifecycle
How to structure a productive pair programming session from start to finish.
1. Before You Start
Get routing and context from the hooks system:
# Register the task and get agent/model recommendations
npx monomind hooks pre-task -d "Pair programming: implement [feature]"
Load relevant context from memory:
npx monomind memory search --query "[feature domain]" --type hybrid
2. Set Session Context
Tell Claude everything it needs to know upfront:
Context for this session:
- Goal: [what we're building]
- Mode: [driver/navigator/TDD/review]
- Stack: [language, framework, key libraries]
- Constraints: [any architectural decisions already made]
- Focus: [what matters most — correctness / speed / learning]
The more context upfront, the less correction mid-session.
3. During the Session
Keeping the session focused:
- One concern at a time — don't mix "implement auth" with "also fix the bug in payments"
- Check in at logical breakpoints: "Before we continue, does this approach make sense?"
- If you get stuck: "I'm not sure how to handle [edge case]. What are our options?"
Real-time quality checks:
# Watch system status during long sessions
npx monomind status --watch
# Check test state
# (run your test suite normally)
Capture decisions as you go:
# Store important patterns discovered during session
npx monomind memory store --key "session-[date]-[feature]" \
--value "[what we decided and why]" \
--namespace "decisions"
4. Breakpoints and Handoffs
Use natural stopping points:
- After implementing a complete unit (function, class, endpoint)
- Before switching between subsystems
- When you need to run tests and wait
At each breakpoint:
"Summarize what we've done so far and what comes next."
This keeps both you and Claude aligned on state.
5. End of Session
Record outcomes for future sessions:
# Record task completion
npx monomind hooks post-task --task-id <id> --success true
# Store any patterns worth remembering
npx monomind memory store \
--key "pattern-[name]" \
--value "[the pattern we found/confirmed]" \
--namespace "patterns"
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 · 125 lines · 33 tokens per session scan A 5a361147ea16
pair:session is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 835 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
prune
Delete pending instincts older than 30 days that were never promoted.
ordenar
Grupo: Trabajo con el framework En una frase: Capturar archivos, carpetas y dumps del chat — documentar en la capa correcta y dejar manifest recuperable. Cuándo: Volcás mucha data, briefs, notas o paths y querés que el DT clasifique, documente e indexe para reutilizar. Quién: Cualquier operador del repo.
cerebro-profesional
Grupo: Módulos del segundo cerebro En una frase: Agenda de reuniones, contactos, equipos y búsqueda profesional. Cuándo: Querés explorar notas Meet, timelines por persona o filtrar por proyecto. Quién: Cualquier operador del repo.
cerebro-work
Grupo: Módulos del segundo cerebro En una frase: Sync cerebro profesional — atajo CerebroWork (script en raíz). Cuándo: Querés correr el sync Meet→Markdown sin recordar paths; ritual rápido post-OAuth. Quién: Cualquier operador del repo.
start
Grupo: Módulos del segundo cerebro En una frase: Abrir Tools Hub — índice interactivo de herramientas con búsqueda. Cuándo: Querés ver o encontrar rápido tus tools y commands del segundo cerebro. Quién: Cualquier operador del repo.
checklist
Generate a custom checklist for the current feature based on user requirements.