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 commands/xbim08/awesome-claude-code-plugins/optimizegit clone --depth 1 https://github.com/xbim08/awesome-claude-code-pluginsWrote 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/xbim08/awesome-claude-code-plugins/optimize)<a href="https://agentmods.dev/commands/xbim08/awesome-claude-code-plugins/optimize"><img src="https://agentmods.dev/badge/commands/xbim08/awesome-claude-code-plugins/optimize.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.00005 | $0.00178 |
| Opus 5 | $0.00003 | $0.00089 |
| Sonnet 5 | $0.00001 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
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 2d 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.
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
Context
- File size: !
du -h $ARGUMENTS 2>/dev/null || echo "File not specified" - Line count: !
wc -l $ARGUMENTS 2>/dev/null || echo "File not specified"
Your task
Analyze and optimize: @$ARGUMENTS
Focus areas:
- Algorithm efficiency: Improve time/space complexity
- Memory usage: Reduce memory footprint
- I/O operations: Optimize file/network operations
- Caching opportunities: Identify cacheable operations
- Lazy loading: Implement lazy loading where beneficial
- Bundle optimization: Reduce bundle size (if applicable)
Provide before/after comparisons and performance impact estimates.
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.
- 2d ago First seen · 23 lines · 5 tokens per session scan A db0e5221e55c
optimize is a command published in the GitHub repository xbim08/awesome-claude-code-plugins (10 stars, last pushed today), licensed Apache-2.0. It adds 5 tokens to every session and 178 once invoked, about $0.0000 per session on Opus 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-09-04.
Other commands, from other repositories
bug-detective
Systematic debugging assistant with troubleshooting steps.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
claudex
Claude writes, Codex reviews, iterate until both agree — then ship with love.
debate
The debate — Claude and Codex argue a design decision from opposite corners, you arbitrate.
remember
Save the current session to persistent context memory.
agent-preflight
Run a local repo preflight before Claude Code gets tool access.