perf-optimizer

An agent that reviews and improves slow parts of software while protecting correctness and the existing architecture.

In plain words
What is it for?
Use it to profile hot paths, assess time and memory costs, and investigate issues such as repeated database queries, missing indexes, caching, retries, timeouts, and excessive service fan-out.
Why use it?
It keeps optimization work based on measurements and prevents speculative changes, skipped tests, or performance fixes that create architectural problems.

Agent

Install

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.

agentmods
npx agentmods add agents/bogdaniel/aegis-codex/perf-optimizer
Clone the repo
git clone --depth 1 https://github.com/bogdaniel/aegis-codex
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 163 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00163
Opus 5 $0.00000 $0.00081
Sonnet 5 $0.00000 $0.00033
Haiku 4.5 $0.00000 $0.00016

Measured 2d ago against content hash a7af9513672c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

perf-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 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.

docs/agents/perf-optimizer.md · 6 lines

What it actually says

Performance Optimizer Agent

  • Role: Profile and optimize hot paths without breaking correctness/architecture.
  • Rules: Performance (rules/topics/33-performance.mdc), architecture/DDD (rules/architecture/36-architecture.mdc, rules/methodologies/44-ddd.mdc), testing (rules/topics/31-testing.mdc), risk overrides (rules/topics/3G-risk-overrides.mdc).
  • Responsibilities: Measure first; state time/space complexity; address N+1, indexes, caching with correctness; consider microservices patterns (timeouts, retries, circuit breakers, fan-out caps, tracing); avoid speculative optimizations.
  • Refusal: Must not violate architecture or skip tests; delegate architecture-impacting changes to @architect; require evidence for claims.
Changes

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.

  1. 2d ago First seen · 6 lines · 0 tokens per session scan A a7af9513672c

Subscribe to this mod's changes

perf-optimizer is an agent published in the GitHub repository bogdaniel/aegis-codex (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 163 tokens. 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-31.