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 skills/arabelatso/skills-4-se/code-optimizernpx skills add ArabelaTso/Skills-4-SE --skill code-optimizergit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/skills/arabelatso/skills-4-se/code-optimizer)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/code-optimizer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/code-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 | $0.00076 | $0.03209 |
| Opus 5 | $0.00038 | $0.01605 |
| Sonnet 5 | $0.00015 | $0.00642 |
| Haiku 4.5 | $0.00008 | $0.00321 |
Grade A, and why
code-optimizer 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 4d 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 — 542 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Optimizer
Improve code performance, memory usage, and efficiency through systematic optimization.
Core Capabilities
This skill helps optimize code by:
- Analyzing performance bottlenecks - Identifying slow or inefficient code
- Suggesting optimizations - Providing concrete improvements with examples
- Explaining trade-offs - Describing benefits and potential drawbacks
- Measuring impact - Estimating performance gains
- Preserving correctness - Ensuring optimizations don't change behavior
Optimization Workflow
Step 1: Identify Optimization Opportunities
Analyze code to find performance bottlenecks.
Look for:
- Nested loops (O(n²) or worse complexity)
- Repeated expensive operations
- Inefficient data structures
- Unnecessary object creation
- Database N+1 queries
- Blocking I/O operations
- Memory leaks or excessive allocation
Quick Analysis Questions:
- What is the time complexity? Can it be reduced?
- Are there repeated calculations that could be cached?
- Is the right data structure being used?
- Are there unnecessary copies or allocations?
- Can operations be batched or parallelized?
Step 2: Categorize the Optimization
Determine the type of optimization needed.
Execution Speed:
- Algorithm optimization (better complexity)
- Loop optimization
- Caching/memoization
- Lazy evaluation
- Parallel processing
Memory Usage:
- Reduce object creation
- Use generators/streams instead of lists
- Clear references to enable garbage collection
- Use appropriate data structures
- Avoid memory leaks
Database Operations:
- Query optimization (indexes, joins)
- Batch operations
- Connection pooling
- Caching
- Reduce round trips
I/O Operations:
- Buffering
- Async/non-blocking I/O
- Batch requests
- Compression
- Caching
Step 3: Propose Optimization with Examples
Provide before/after code with clear explanations.
Optimization Template:
## Optimization: [Brief Description]
### Before (Inefficient)
```[language]
[original code]
Issues:
- Issue 1: [Problem description]
- Issue 2: [Problem description]
Complexity: O([complexity]) Performance: [estimated time/memory]
After (Optimized)
[optimized code]
Improvements:
- Improvement 1: [What changed]
- Improvement 2: [What changed]
Complexity: O([new complexity]) Performance: [estimated time/memory] Gain: [X% faster / Y% less memory]
Why This Works
[Detailed explanation of the optimization]
Trade-offs
Pros:
- [Benefit 1]
- [Benefit 2]
Cons:
- [Drawback 1, if any]
- [Drawback 2, if any]
When to Use
- Use when: [scenario]
- Avoid when: [scenario]
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.
- 4d ago First seen · 542 lines · 76 tokens per session scan A 34f178e8a592
code-optimizer is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (247 stars, last pushed 13d ago), licensed Apache-2.0. It adds 76 tokens to every session and 3,209 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
memory-search
Query the raw trajectory SQLite database directly when the built-in memory and history tools are insufficient. Use when you need structured analysis across sessions: finding repeated errors, grouping tool calls by pattern, verifying what was actually executed, or locating specific past commands/decisions that text…
caching-strategies
CDN, Redis, in-memory cache, cache invalidation, and distributed caching patterns.
rudder-performance-maintainer
Use for repeatable Rudder performance audits, regressions, profiling, optimization proposals, or implementation verification across Messenger, Chat, Issues, Runs, Desktop, API payloads, database queries, rendering, memory, and high-volume workflows. Trigger for daily performance checks, product latency or memory…
hermes-mnemosyne
Mnemosyne is Hermes' primary local-first memory engine — SQLite with vector + FTS5 hybrid search, 19+ tools, auto-consolidation, and a standalone CLI. It's a pip-installed plugin (not a built-in toolset) discovered via $HERMESHOME/plugins/mnemosyne/.
chromadb
Manage the ChromaDB vector database that stores the ecosystem's persistent memory. Use when user asks to check memory storage, backup memory, search stored entries, delete entries, or reset the vector database. Do NOT use for general question answering about past sessions (use the memory skill for that).
memory-layer
Standalone persistent memory for Pi — smart search, symbol clustering, dedup, auto-recovery, trust scoring. Zero Python dependency.