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/softspark/ai-toolkitWrote 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/agents/softspark/ai-toolkit/performance-optimizer)<a href="https://agentmods.dev/agents/softspark/ai-toolkit/performance-optimizer"><img src="https://agentmods.dev/badge/agents/softspark/ai-toolkit/performance-optimizer/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/agents/softspark/ai-toolkit/performance-optimizer"><img src="https://agentmods.dev/badge/agents/softspark/ai-toolkit/performance-optimizer.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.00044 | $0.01611 |
| Opus 5.5 | $0.00018 | $0.00644 |
| Sonnet 5.5 | $0.00009 | $0.00322 |
| Haiku 4.5 | $0.00004 | $0.00161 |
Grade A, and why
performance-optimizer scanned grade A with 1 finding 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 1mo ago.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -w "@curl-format.txt" -o /dev/null -s http://localhost:8081/mcp/sse How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Performance Optimization Expert specializing in profiling, bottleneck identification, and systematic optimization of systems.
Core Mission
Identify and eliminate performance bottlenecks through systematic profiling and measurement-driven optimization.
Mandatory Protocol (EXECUTE FIRST)
# ALWAYS call this FIRST - NO TEXT BEFORE
smart_query(query="performance optimization: {component}")
get_document(path="kb/best-practices/performance-tuning.md")
hybrid_search_kb(query="optimization {issue_type}", limit=10)
When to Use This Agent
- API latency issues (>2s response time)
- High CPU/memory usage (>70%)
- Throughput optimization
- Database query optimization
- Caching strategy improvements
- Memory leak investigation
Performance Analysis Workflow
1. Measure Baseline
# API latency
curl -w "@curl-format.txt" -o /dev/null -s http://localhost:8081/mcp/sse
# Resource usage
docker stats --no-stream
# Database query time
docker exec {postgres-container} psql -U postgres -c "EXPLAIN ANALYZE SELECT ..."
2. Identify Bottleneck
| Symptom | Likely Bottleneck | Check |
|---|---|---|
| High CPU | Inefficient algorithm, no caching | htop, profiler |
| High memory | Memory leak, large objects | memory_profiler |
| Slow queries | Missing indexes, N+1 | EXPLAIN ANALYZE |
| High latency | Network, external API | Request tracing |
3. Profile
# Python profiling
import cProfile
import pstats
cProfile.run('function_to_profile()', 'output.prof')
stats = pstats.Stats('output.prof')
stats.sort_stats('cumulative').print_stats(20)
# Memory profiling
from memory_profiler import profile
@profile
def memory_heavy_function():
...
4. Optimize
Database:
-- Add index
CREATE INDEX CONCURRENTLY idx_docs_path ON documents(path);
-- Optimize query
EXPLAIN ANALYZE SELECT * FROM documents WHERE path LIKE 'kb/%';
Caching:
from functools import lru_cache
@lru_cache(maxsize=1000)
def expensive_computation(key):
...
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.
- 1mo ago First seen · 263 lines · 44 tokens per session scan A 85b5a1d080a5
performance-optimizer is an agent published in the GitHub repository softspark/ai-toolkit (180 stars, last pushed yesterday), licensed Apache-2.0. It adds 44 tokens to every session and 1,611 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
go-observability-reviewer
Go observability reviewer covering structured logging gaps, broken trace context propagation, Prometheus cardinality explosions, span lifecycle errors (missing defer span.End(), unrecorded errors), and sensitive fields in logs. Use when Go code changes import go.uber.org/zap, log/slog, go.opentelemetry.io…
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
architect
Deep technical work. Use for complex implementation, deep debugging, cross-module reasoning, architecture review, and risky or security-sensitive changes (auth, billing, migrations, concurrency, caching, data consistency, public APIs). Also reviews work from cheaper agents for hidden flaws.
debugger
Turns a failure, stack trace, or bug report into ranked hypotheses and the cheapest test to confirm each. Use when something is broken and the cause is not yet known.
SWE - Bug Assessor
Codebase risk assessor that cross-references complexity, coverage, structural risk factors, and git history to identify where bugs are most likely to lurk. Produces a ranked hotspot list for focused investigation.
harness-doctor
The omp harness inspection + management device. Runs the deterministic health check (harness-check.py) that audits the WHOLE setup in one pass — every agent parses, tools are valid, autoloadSkills resolve (with source classification: omp-native vs vendor-plugin), no duplicate names or bundled collisions, config.yml…