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.
npx agentmods add agents/bejranonda/llm-autonomous-agent-plugin-for-claude/performance-optimizergit clone --depth 1 https://github.com/bejranonda/LLM-Autonomous-Agent-Plugin-for-ClaudeWrote 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/bejranonda/llm-autonomous-agent-plugin-for-claude/performance-optimizer)<a href="https://agentmods.dev/agents/bejranonda/llm-autonomous-agent-plugin-for-claude/performance-optimizer"><img src="https://agentmods.dev/badge/agents/bejranonda/llm-autonomous-agent-plugin-for-claude/performance-optimizer.svg" alt="Measured on agentmods" 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.00023 | $0.04017 |
| Opus 5 | $0.00012 | $0.02008 |
| Sonnet 5 | $0.00005 | $0.00803 |
| Haiku 4.5 | $0.00002 | $0.00402 |
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 6d 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.
response = requests.get('http://api.example.com/data') The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 6d ago First seen · 610 lines · 23 tokens per session scan A ae739ca80424
performance-optimizer is an agent published in the GitHub repository bejranonda/LLM-Autonomous-Agent-Plugin-for-Claude (28 stars, last pushed 2mo ago), with no licence file. It adds 23 tokens to every session and 4,017 once invoked, about $0.0001 per session on Opus 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
usage-finder
MUST BE USED for finding code usages and building usage maps. USE PROACTIVELY when user asks "where is X used", "find usages", "what calls this", "build usage map", "map class usages", or needs to track dependencies. Expert at finding functions, methods, classes, variables across codebases and generating structured…
performance-analyzer
MUST BE USED for code performance issues. USE PROACTIVELY when user mentions "slow code", "code bottleneck", "optimize code", "N+1 queries", "algorithm performance", "memory leak", "inefficient code", or database performance. Identifies algorithmic issues, database problems, memory leaks, and code optimization…
dependency-analyzer
MUST BE USED for dependency analysis. USE PROACTIVELY when user asks about "dependencies", "circular deps", "security vulnerabilities", "bundle size", "npm audit", or package issues. Supports npm, pip, go modules, maven, cargo, composer.
code-analyst
MUST BE USED for code file analysis. Performs deep analysis of architecture, patterns, dependencies, complexity, issues, and recommendations. USE PROACTIVELY when user asks to analyze, understand, review, investigate, rework, improve, or check any code file, module, README, or documentation.
brahma-investigator
Root cause analysis and debugging specialist with Anthropic think protocol and 3-retry limit. Focuses on systematic problem diagnosis, error tracing, and fix validation. Use for complex bugs and system failures.
self-debug
Diagnoses and recovers from agent failures using structured recovery protocol.