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/loulanyue/awesome-claude-notesWrote 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/loulanyue/awesome-claude-notes/prompt-optimize)<a href="https://agentmods.dev/commands/loulanyue/awesome-claude-notes/prompt-optimize"><img src="https://agentmods.dev/badge/commands/loulanyue/awesome-claude-notes/prompt-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/loulanyue/awesome-claude-notes/prompt-optimize"><img src="https://agentmods.dev/badge/commands/loulanyue/awesome-claude-notes/prompt-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.00030 | $0.00497 |
| Opus 5 | $0.00015 | $0.00249 |
| Sonnet 5 | $0.00006 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
prompt-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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ccc-prompt-optimize — 89% identical, 9 lines differ
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/prompt-optimize
Analyze and optimize the following prompt for maximum ECC leverage.
Your Task
Apply the prompt-optimizer skill to the user's input below. Follow the 6-phase analysis pipeline:
- Project Detection — Read CLAUDE.md, detect tech stack from project files (package.json, go.mod, pyproject.toml, etc.)
- Intent Detection — Classify the task type (new feature, bug fix, refactor, research, testing, review, documentation, infrastructure, design)
- Scope Assessment — Evaluate complexity (TRIVIAL / LOW / MEDIUM / HIGH / EPIC), using codebase size as signal if detected
- ECC Component Matching — Map to specific skills, commands, agents, and model tier
- Missing Context Detection — Identify gaps. If 3+ critical items missing, ask the user to clarify before generating
- Workflow & Model — Determine lifecycle position, recommend model tier, and split into multiple prompts if HIGH/EPIC
Output Requirements
- Present diagnosis, recommended ECC components, and an optimized prompt using the Output Format from the prompt-optimizer skill
- Provide both Full Version (detailed) and Quick Version (compact, varied by intent type)
- Respond in the same language as the user's input
- The optimized prompt must be complete and ready to copy-paste into a new session
- End with a footer offering adjustment or a clear next step for starting a separate execution request
CRITICAL
Do NOT execute the user's task. Output ONLY the analysis and optimized prompt.
If the user asks for direct execution, explain that /prompt-optimize only produces advisory output and tell them to start a normal task request instead.
Note: blueprint is a skill, not a slash command. Write "Use the blueprint skill"
instead of presenting it as a /... command.
User Input
$ARGUMENTS
Navigation
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.
- 5d ago First seen · 46 lines · 30 tokens per session scan A 94b032d0a254
prompt-optimize is a command published in the GitHub repository loulanyue/awesome-claude-notes (270 stars, last pushed 5d ago), licensed MIT. It adds 30 tokens to every session and 497 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
security-scan
Run security audit on codebase.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
standardize-claude-md
Add missing toolkit sections (Related Global Rules, Quick Start) to existing CLAUDE.md.
help
Explain Ralph Wiggum technique and available commands.