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/obiwancenobi/klambenWrote 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/obiwancenobi/klamben/optimize)<a href="https://agentmods.dev/commands/obiwancenobi/klamben/optimize"><img src="https://agentmods.dev/badge/commands/obiwancenobi/klamben/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/obiwancenobi/klamben/optimize"><img src="https://agentmods.dev/badge/commands/obiwancenobi/klamben/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.00023 | $0.00319 |
| Opus 5.5 | $0.00009 | $0.00128 |
| Sonnet 5.5 | $0.00005 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
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
/optimize
Performance cleanup. Mechanical, safe changes only.
When to use
- Jank on scroll
- Slow rebuilds
- Before shipping to low-end devices
/auditflags code-quality/missing-const
Actions
- Check design context: If
.klamben.mdexists in the project root, read it first. Apply the project's brand, platform targets, accessibility tier, and existing patterns to your work below. - Add
constto every eligible constructor ListView.builderfor lists > 10 itemsRepaintBoundaryaround animated or expensive subtreescached_network_imagefor network images (add to pubspec if needed)ValueListenableBuilder/AnimatedBuilderinstead ofsetStateon animations- Lazy loading —
ListView.builderwithitemCountoverListView(children: map(...).toList()) - Avoid
Opacityfor fade animations — preferFadeTransition
Do NOT
- Cache data without understanding invalidation
- Add profile-mode benchmarks unless user asks
- Change business logic
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 · 40 lines · 23 tokens per session scan A 00ea753a99bc
optimize is a command published in the GitHub repository obiwancenobi/klamben (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 319 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-08-31.
Other commands, from other repositories
speckit.zuraffa.entity
Create Zorphy entities with fields.
speckit.zuraffa.generate-commands
Regenerate all extension command files from zfa manifest.
audit
Audit the current codebase for Flutter best practice violations.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.