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 skills add IchenDEV/prompt-optimizer-plugins --skill optimize-claude-opus-5-promptsgit clone --depth 1 https://github.com/IchenDEV/prompt-optimizer-pluginsWrote 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/ichendev/prompt-optimizer-plugins/optimize-claude-opus-5-prompts)<a href="https://agentmods.dev/skills/ichendev/prompt-optimizer-plugins/optimize-claude-opus-5-prompts"><img src="https://agentmods.dev/badge/skills/ichendev/prompt-optimizer-plugins/optimize-claude-opus-5-prompts/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/skills/ichendev/prompt-optimizer-plugins/optimize-claude-opus-5-prompts"><img src="https://agentmods.dev/badge/skills/ichendev/prompt-optimizer-plugins/optimize-claude-opus-5-prompts.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.00182 | $0.03095 |
| Opus 5 | $0.00091 | $0.01548 |
| Sonnet 5 | $0.00036 | $0.00619 |
| Haiku 4.5 | $0.00018 | $0.00310 |
Grade A, and why
optimize-claude-opus-5-prompts 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 10d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimize Claude Opus 5 Prompts
Turn rough ideas and existing prompt stacks into copy-ready prompts for Claude Opus 5. Preserve the user's intent and hard constraints, clarify genuinely blocking gaps, and keep the result no more elaborate than the task requires.
Opus 5 performs well out of the box on prompts written for Claude Opus 4.8. Most real optimization here is subtractive plus a few targeted behavior instructions, not a rewrite into a larger template.
Use the official basis
Read references/official-guidance.md for model-specific rationale, runtime settings, and migration details. Read references/snippets.md for the copy-ready instruction blocks from Anthropic's guide. Treat the listed URLs as canonical and the prose as a dated working summary; fetch the live pages before making claims about current model IDs, parameters, availability, limits, or pricing.
Use the official model name Claude Opus 5 and the API model ID claude-opus-5. Treat Opus5, opus-5, and O5 as spelling variants unless context indicates a different product.
Follow the workflow
1. Capture the prompt contract
Identify the following from the user's message, pasted prompt, or referenced file:
- the user-visible outcome and why it matters;
- the inputs, source material, and context Claude will receive;
- hard constraints, facts, policies, and values to preserve;
- the required output, audience, language, and level of detail;
- tools, evidence, or verification the task genuinely depends on;
- whether Claude should assess, recommend, draft, implement, or take external action;
- authorized actions and actions that require approval;
- stopping and fallback behavior when a dependency is unavailable;
- which Opus 5 behavior the user has actually observed as a problem, and whether the prompt was carried over from Opus 4.8 or an earlier model.
Treat these as diagnostic dimensions, not mandatory prompt sections. Keep a simple prompt simple.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 179 lines · 182 tokens per session scan A 98a26b54de74
optimize-claude-opus-5-prompts is a skill published in the GitHub repository IchenDEV/prompt-optimizer-plugins (6 stars, last pushed 3d ago), licensed MIT. It adds 182 tokens to every session and 3,095 once invoked, about $0.0009 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-31.
Other skills, from other repositories
instructor
Extract structured data from LLM responses with Pydantic validation, retry failed extractions automatically, parse complex JSON with type safety, and stream partial results with Instructor - battle-tested structured output library.
build-dotnet-agent-service
Build a local-first F# or C# Semantic Kernel agent service with explicit tools, model capability checks, evaluation fixtures, and draft-before-write promotion.
instructor
Extract structured data from LLM responses with Pydantic validation, retry failed extractions automatically, parse complex JSON with type safety, and stream partial results with Instructor - battle-tested structured output library.
analyze-prompt
Use when the user wants to review, score, or improve how they write prompts; when coaching prompt quality; or when tracking prompting mistakes over a session. Keywords: prompt analysis, prompt coaching, how should I ask, rate my prompt, am I prompting well, prompt statistics, prompt score.
prompt-mini
Forges weak Claude Code prompts into structured, credit-saving, framework-aware prompts. Use when prompts are vague, missing scope, or mention a stack without clear task definition.
prompt-report
Use when the user wants an end-of-session summary of their prompting: overall stats, best and worst prompts, biggest recurring mistake, improvement curve, and personalized recommendations. Keywords: prompt report, session summary, how did I do, my prompting stats, prompt scorecard, prompting progress.