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/status)<a href="https://agentmods.dev/commands/monoes/monomind/status"><img src="https://agentmods.dev/badge/commands/monoes/monomind/status/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/status"><img src="https://agentmods.dev/badge/commands/monoes/monomind/status.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.00019 | $0.00710 |
| Opus 5.5 | $0.00008 | $0.00284 |
| Sonnet 5.5 | $0.00004 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
monitoring:status 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
status
Show system status — agents, tasks, memory, and MCP server. The primary monitoring command.
Usage
npx monomind status [options]
npx monomind status <subcommand>
Options
| Flag | Short | Type | Default | Description |
|---|---|---|---|---|
--watch |
-w |
boolean | false |
Continuously refresh status (live view) |
--interval |
-i |
number | 2 |
Refresh interval in seconds (watch mode) |
--health-check |
— | boolean | false |
Run structured health checks and exit |
--format |
— | string | — | Output format: json |
Subcommands
| Subcommand | Description |
|---|---|
status agents |
Detailed agent status table (ID, type, current task, uptime, success rate) |
status tasks |
Detailed task status table (ID, type, priority, agent, progress) |
status memory |
Memory backend stats (entries, size, HNSW, performance metrics) |
Examples
# One-shot status snapshot
npx monomind status
# Live watch mode (refreshes every 2s)
npx monomind status --watch
# Watch with custom interval
npx monomind status --watch -i 5
# Health checks with pass/warn/fail output
npx monomind status --health-check
# JSON output for scripting
npx monomind status --format json
# Detailed agent table
npx monomind status agents
# Detailed task table
npx monomind status tasks
# Memory backend details
npx monomind status memory
Status Display Sections
- Agents — agents recorded in the agent store (terminated ones left out)
- Tasks — pending / running / completed / failed / total
- Memory — backend, entries, size, search time, cache hit rate
- MCP Server — running state, transport, port
- Performance — CPU usage, memory usage, vector search speed
Health Check Mode
--health-check runs structured checks and exits with code 0 (all pass) or 1 (any fail):
| Check | Pass Condition |
|---|---|
| System Running | daemon process alive |
| Agents Available | recorded agents > 0 |
| MCP Server | running |
| Memory Backend | backend != none |
| Task Success Rate | < 5% failure rate |
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 · 104 lines · 19 tokens per session scan A f67a896a47fd
monitoring:status is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 710 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.