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/agent-metrics)<a href="https://agentmods.dev/commands/monoes/monomind/agent-metrics"><img src="https://agentmods.dev/badge/commands/monoes/monomind/agent-metrics/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/agent-metrics"><img src="https://agentmods.dev/badge/commands/monoes/monomind/agent-metrics.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.00025 | $0.00450 |
| Opus 5.5 | $0.00010 | $0.00180 |
| Sonnet 5.5 | $0.00005 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
monitoring:agent-metrics 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.
What it actually says
agent metrics
Show agent performance metrics — tasks completed, success rate, and memory vectors by agent type.
Usage
npx monomind agent metrics [agentId] [options]
The optional agentId positional argument filters to a specific agent. Omit for all agents.
Options
| Flag | Short | Type | Default | Description |
|---|---|---|---|---|
--period |
-p |
string | 24h |
Time period: 1h, 24h, 7d, 30d |
--format |
— | string | — | Output format: json |
Examples
# All agents — last 24 hours
npx monomind agent metrics
# Last hour
npx monomind agent metrics --period 1h
# Last 7 days
npx monomind agent metrics -p 7d
# Specific agent
npx monomind agent metrics agent-001
# JSON output
npx monomind agent metrics --format json
Output Sections
Summary table — total agents, active agents, tasks completed, average success rate, memory vector count
By Agent Type table — per-type breakdown: count, tasks completed, success rate
Memory — vector count and search backend (HNSW-indexed once vectors exist)
Data Source
Metrics are read from .swarm/agents/ state files and .swarm/swarm-activity.json. If no agents have been spawned yet, the output will note this with a suggestion to run agent spawn.
MCP Tool
mcp__monomind__agent_status({ agentId: "agent-001" })
See Also
status agents— live agent status tableagent health— per-agent health check with--watchmodeagent list— list all 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 · 67 lines · 25 tokens per session scan A d7efaf5eb707
monitoring:agent-metrics is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 25 tokens to every session and 450 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.