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/performance-optimize)<a href="https://agentmods.dev/commands/monoes/monomind/performance-optimize"><img src="https://agentmods.dev/badge/commands/monoes/monomind/performance-optimize/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/performance-optimize"><img src="https://agentmods.dev/badge/commands/monoes/monomind/performance-optimize.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.00036 | $0.00500 |
| Opus 5.5 | $0.00014 | $0.00200 |
| Sonnet 5.5 | $0.00007 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
optimization:performance-optimize 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
performance optimize
Analyze system-level performance and get optimization recommendations — memory, latency, and throughput.
There is no optimize subcommand of monomind performance — this is invoked
directly as an MCP tool call. It is a rule-based recommendation engine over
real CPU, memory, and disk readings: only garbage collection and probe-file
cleanup are applied automatically (with aggressive: true); everything else is
returned as a recommendation.
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
target |
string | all |
Optimization target: memory, latency, throughput, all |
aggressive |
boolean | false |
Force GC (needs --expose-gc) and clear perf probe files |
Examples
// Analyze and show recommendations
mcp__monomind__performance_optimize({ target: "all" })
// Memory-specific recommendations, forcing a GC pass
mcp__monomind__performance_optimize({ target: "memory", aggressive: true })
// Latency recommendations (disk I/O)
mcp__monomind__performance_optimize({ target: "latency" })
Optimization Targets
| Target | What It Checks |
|---|---|
memory |
System memory pressure, HNSW rebuild recommendation, forced GC (aggressive) |
latency |
Disk I/O latency, batching of file operations |
throughput |
Batch size for the CPU core count, CPU load throttling |
all |
All of the above |
Related Commands
# Find bottlenecks before optimizing
npx monomind performance bottleneck
# Run benchmarks to measure before/after
npx monomind performance benchmark --suite all
# View current performance metrics
npx monomind performance metrics
See Also
performance bottleneck— diagnose what to optimize firstperformance benchmark— measure optimization impactperformance metrics— track performance over timehooks intelligence optimize— compact the local pattern store
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 · 64 lines · 36 tokens per session scan A 062aeb5df9fb
optimization:performance-optimize is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 500 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.