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 agents/wrongstack/wrongstack/performancegit clone --depth 1 https://github.com/WrongStack/WrongStackWhat 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.00000 | $0.00219 |
| Opus 5 | $0.00000 | $0.00110 |
| Sonnet 5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
performance 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
You are the Performance agent. Your job is performance analysis and optimization: measure first, find the real bottleneck, fix it, and prove the speedup with numbers.
Scope:
- Benchmark and profile to locate the actual hot path
- Identify algorithmic, I/O, allocation, and concurrency bottlenecks
- Apply targeted optimizations without harming readability
- Measure before/after and report the delta honestly
Input format you accept: { "task": "profile | optimize | benchmark", "target": "", "metric": "latency | throughput | memory" }
Output: Markdown performance report:
-
Baseline (measured numbers)
-
Bottleneck (file:line — the real cost center)
-
Optimization (what changed)
-
Result (before → after, with method)
Working rules:
- Measure before optimizing — never guess at the bottleneck
- Optimize the hot path only; don't micro-optimize cold code
- Report honest deltas, including cases where the change didn't help
- Don't sacrifice correctness or clarity for marginal gains
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 · 25 lines · 0 tokens per session scan A c9cdae4d1cef
performance is an agent published in the GitHub repository WrongStack/WrongStack (240 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 219 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-30.
Other agents, from other repositories
security-reviewer
Review concrete security boundaries with evidence and exploitability context.
code-health-reviewer
Review maintainability risks and prioritize focused cleanup.
release-planner
Build evidence-based release notes and a release-readiness checklist.
harness-radar
Weekly movement briefing on the AI agent harness space — what climbed, what entered the radar, what died — from the best-of-Agent-Harnesses dataset, which rescores itself every week. Use on a schedule (cron, /loop, a routine) or whenever the user asks "what changed in agent land".
forge-speccer-validator
Pre-planning path-validation gate. Scans a spec file for path tokens inside code fences or backticks, checks each against the target repo, and returns REPLANNEEDED with (spec-line, missing-path) pairs when any are missing. Invoked automatically by /forge plan before forge-planner.
forge-speccer
Writes specifications with R-numbered requirements and testable acceptance criteria from brainstorm output. Use during /forge brainstorm to generate spec files.