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/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/performance-optimization)<a href="https://agentmods.dev/commands/saajunaid/caddis-plugin/performance-optimization"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/performance-optimization/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/saajunaid/caddis-plugin/performance-optimization"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/performance-optimization.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.00017 | $0.00961 |
| Opus 5.5 | $0.00007 | $0.00384 |
| Sonnet 5.5 | $0.00003 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
performance-optimization 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Optimization Prompt
Use this prompt when you need to optimize code for better performance.
Context Template
I need to optimize [FUNCTION/MODULE/QUERY] for better performance.
## Current Situation
- Current performance: [e.g., 5 seconds response time]
- Target performance: [e.g., < 500ms response time]
- Volume: [e.g., 10,000 records, 100 concurrent users]
## Constraints
- Cannot change: [e.g., database schema, external API]
- Must maintain: [e.g., existing API contract]
- Budget: [e.g., no additional infrastructure]
## What I've Tried
- [List previous optimization attempts]
## Code/Query to Optimize
[Paste the code or query]
Example: SQL Query Optimization
I need to optimize this SQL query for better performance.
## Current Situation
- Current performance: 12 seconds
- Target performance: < 1 second
- Volume: 500,000 records, queried 50 times/hour
## Constraints
- Cannot add new indexes (DBA approval required for production)
- Must return same result set
## What I've Tried
- Added WHERE clause filters
- Reduced SELECT columns
## Query to Optimize
SELECT c.customer_id, c.name,
COUNT(o.order_id) as order_count,
SUM(o.total) as total_spent
FROM customers c
LEFT JOIN orders o ON c.customer_id = o.customer_id
WHERE o.created_at > '2024-01-01'
GROUP BY c.customer_id, c.name
ORDER BY total_spent DESC
Analysis Framework
When optimizing, ask for:
1. Profiling
- Where is time being spent?
- What are the bottlenecks?
- Memory usage patterns?
2. Algorithm Analysis
- Time complexity (O notation)?
- Can we reduce iterations?
- Are there more efficient algorithms?
3. Database Optimization
- Query execution plan analysis
- Index recommendations
- Query restructuring
4. Caching Opportunities
- What data is static or slowly changing?
- What queries are repeated?
- Where can we add memoization?
5. Parallelization
- Can work be distributed?
- Are there independent operations?
- Would async help?
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 · 168 lines · 17 tokens per session scan A 7467af9ccb34
performance-optimization is a command published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 961 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-09-09.
Other commands, from other repositories
debug-screen
Diagnose why the current screen is broken, showing unexpected content, or crashing. Gathers parallel evidence from all layers and applies a targeted fix.
self-healing
Automatically detect and recover from errors without interrupting your flow.
prototype
Command dispatcher for prototype.
specify
Command dispatcher for specify.
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.
postmortem
Generate blameless postmortem documents with timeline, root cause analysis, and action items.