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/start)<a href="https://agentmods.dev/commands/monoes/monomind/start"><img src="https://agentmods.dev/badge/commands/monoes/monomind/start/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/start"><img src="https://agentmods.dev/badge/commands/monoes/monomind/start.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.00037 | $0.00693 |
| Opus 5.5 | $0.00015 | $0.00277 |
| Sonnet 5.5 | $0.00007 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
truth:start 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Truth — System Reliability Assessment
Assess the current health, agent performance, and task quality of the Monomind system.
How to Invoke
Skill("truth:start")
Then describe what you want to assess:
"Run a truth check on the current session." "Show me system health and agent performance." "Check for any reliability issues across active agents."
What Truth Covers
| Area | What to check |
|---|---|
| System health | MCP server status, memory DB, daemon |
| Agent performance | Active agents, task completion rates |
| Neural quality | Pattern confidence scores |
| Security posture | Recent AI defence scan results |
| Performance | Bottlenecks, latency, resource usage |
MCP Tools for Truth Assessment
System Health
// Full system status
mcp__monomind__system_health({})
mcp__monomind__system_status({})
mcp__monomind__system_metrics({})
// MCP server connectivity
mcp__monomind__mcp_status({})
Agent Reliability
// List active agents and their states
mcp__monomind__agent_list({})
mcp__monomind__agent_health({})
Neural Pattern Quality
// Pattern confidence scores
mcp__monomind__hooks_intelligence_stats({ verbose: true })
mcp__monomind__hooks_intelligence_pattern-search({ query: "verification", topK: 10 })
// Hooks intelligence stats (routing accuracy)
mcp__monomind__hooks_intelligence_stats({})
Task Quality
// Recent task outcomes
mcp__monomind__task_summary({})
mcp__monomind__task_summary({})
// Memory store health (memory integrity)
mcp__monomind__memory_health({})
Performance
// Performance bottlenecks
mcp__monomind__performance_bottleneck({ component: "all" })
mcp__monomind__performance_report({ format: "detailed" })
Security
// AI defence stats
mcp__monomind__monofence_stats({})
mcp__monomind__monofence_analyze({ input: "recent session summary" })
Assessment Workflow
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 · 118 lines · 37 tokens per session scan A 569361b0c5b1
truth:start is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 37 tokens to every session and 693 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.