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/rohittcodes/claude-plugin-suiteWrote 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/rohittcodes/claude-plugin-suite/optimize)<a href="https://agentmods.dev/commands/rohittcodes/claude-plugin-suite/optimize"><img src="https://agentmods.dev/badge/commands/rohittcodes/claude-plugin-suite/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/rohittcodes/claude-plugin-suite/optimize"><img src="https://agentmods.dev/badge/commands/rohittcodes/claude-plugin-suite/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.00010 | $0.00462 |
| Opus 5.5 | $0.00004 | $0.00185 |
| Sonnet 5.5 | $0.00002 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Optimization Command
Analyze and optimize code for performance, security, and quality with actionable recommendations.
Context
- Optimization type: $1 (performance|security|quality|all - default: all)
- Target area: $2 (specific file, module, or component)
- Code complexity: !
find . -name "*.js" -o -name "*.ts" -o -name "*.py" | xargs wc -l | tail -1 - Dependencies: @package.json
Optimization Analysis
1. Performance Optimization
- Algorithm efficiency analysis
- Database query optimization
- Memory usage optimization
- Caching strategy implementation
- Bundle size and loading optimization
2. Security Hardening
- Vulnerability assessment and remediation
- Input validation and sanitization
- Authentication and authorization review
- Data protection and encryption
- Security headers and policies
3. Code Quality Improvement
- Code structure and organization
- Design pattern implementation
- Error handling and logging
- Documentation and comments
- Testing coverage and quality
4. Best Practices Implementation
- Coding standards compliance
- Dependency management
- Version control practices
- CI/CD pipeline optimization
- Monitoring and observability
Optimization Metrics
- Performance: Response time, throughput, resource usage
- Security: Vulnerability count, compliance score
- Quality: Code complexity, maintainability index
- Best Practices: Standards compliance, test coverage
Expected Outcome
- Comprehensive optimization report
- Prioritized improvement recommendations
- Performance impact analysis
- Implementation roadmap
Optimization Priorities
- Critical: Security vulnerabilities, performance bottlenecks
- High: Code quality issues, maintainability problems
- Medium: Best practice improvements, optimization opportunities
- Low: Future enhancements, nice-to-have improvements
Implementation Plan
- Immediate fixes for critical issues
- Short-term improvements (1-2 weeks)
- Medium-term optimizations (1-2 months)
- Long-term architectural improvements (3-6 months)
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 · 69 lines · 0 tokens per session scan A 0ee1a451724a
optimize is a command published in the GitHub repository rohittcodes/claude-plugin-suite (29 stars, last pushed 1y ago), licensed MIT. It adds 10 tokens to every session and 462 once invoked, about $0.0000 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-09-21.
optimize compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| optimizerohittcodes/claude-plugin-suite | Command | 29 | 1y ago | MIT | A | 10 | Claude Code |
| qa-changesOpenHands/extensions | Command | 184 | 2d ago | MIT | A | 63 | Claude Code |
| react-nativegetsentry/toolkit | Command | 964 | today | none | A | 0 | Claude Code |
| auditar-cascadingluanpdd/kit-mcp | Command | 5 | today | MIT | A | 54 | Claude Code |
| http-serviceMadAppGang/magus | Command | 14 | today | MIT | A | 27 | Claude Code |
| doctordoncheli/don-cheli-sdd | Command | 59 | 3mo ago | Apache-2.0 | A | 76 | Claude Code |
| doctorfatihkan/badi | Command | 8 | 1mo ago | MIT | A | 0 | Claude Code |