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/wesammustafa/opencode-primerWrote 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/wesammustafa/opencode-primer/optimize)<a href="https://agentmods.dev/commands/wesammustafa/opencode-primer/optimize"><img src="https://agentmods.dev/badge/commands/wesammustafa/opencode-primer/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/wesammustafa/opencode-primer/optimize"><img src="https://agentmods.dev/badge/commands/wesammustafa/opencode-primer/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.00303 |
| Opus 5.5 | $0.00004 | $0.00121 |
| Sonnet 5.5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
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.
What it actually says
Analyze the target for performance issues: $ARGUMENTS (or the current branch's changes if empty).
Cover these dimensions in this order:
- Algorithmic — wrong data structure, O(n²) where O(n) is possible, repeated work.
- I/O — N+1 queries, missing indexes, sync calls on hot paths, unbatched network requests.
- Memory — unbounded growth, leaks, large in-memory snapshots that could stream.
- Frontend (if applicable) — re-render cascades, large bundles, unmemoized expensive renders, blocking main-thread work.
- Micro-optimizations — only if (1)–(4) are clean and the call site is genuinely hot.
For each suggestion, output:
[Impact] <summary>
Where: <file:line>
Before: <snippet>
After: <snippet>
Why: <one sentence — what's faster and roughly by how much>
Impact tiers: High (>10× or removes the bottleneck) · Medium (2–10×) · Low (small constant factor).
Don't make the changes yet. End by asking which suggestions to apply.
Optional flag — pass --apply in arguments to skip the discussion and implement the High-impact suggestions directly.
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 · 31 lines · 10 tokens per session scan A 208e2abf8646
optimize is a command published in the GitHub repository wesammustafa/opencode-primer (402 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 303 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-08-30.
Other commands, from other repositories
subagent-diagnose
Multi-agent failure-investigation orchestrator. Parallel to /subagent-implementation — same scratchpad + investigator + builder/surgeon + reviewer + FOLLOWUPS pattern — but starts from a failure, not a spec. Two modes share one loop: ci (failed CI run is the brief seed) and bug (freeform symptom paragraph is the brief…
quick-fix
Implement→review subagent loop with no planning phase, for a fix whose cause is known and whose shape is obvious, however many files it touches. No spec, no worktree, no docs or signals at the end; one audit. Routes to /subagent-diagnose on an unknown cause and to /atomic-plan on an open approach or contract choice.
simplify-transform
Apply verified simplifications with user approval. Part of simplify- family.
dead-code-analyze
Extract, triage, and verify code items for dead code. Part of dead-code- family. Run after /dead-code-setup.
simplify-analyze
Analyze code for simplification opportunities. Part of simplify- family.
simplify
Orchestrates code simplification via verified transformations. Delegates to simplify-analyze, simplify-verify, and simplify-transform.