Awesome Claude Code Toolkit is a curated collection of extensions and configuration for Claude Code, including agents, skills, commands, plugins, hooks, rules, templates, MCP configurations, and companion apps. It is for Claude Code users who want ready-made workflows and integrations for different development tasks. The catalogue add-ons are selected components from this toolkit.
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 commands/rohitg00/awesome-claude-code-toolkit/improve-promptgit clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkitWrote 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/rohitg00/awesome-claude-code-toolkit/improve-prompt)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/improve-prompt"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/improve-prompt.svg" alt="Measured on agentmods" 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.00019 | $0.00384 |
| Opus 5 | $0.00010 | $0.00192 |
| Sonnet 5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
improve-prompt 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 6d 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 and improve an AI prompt for clarity, specificity, and effectiveness.
Steps
- Read the provided prompt or command definition.
- Evaluate against prompt quality dimensions:
- Clarity: Is the instruction unambiguous?
- Specificity: Does it define the expected output format?
- Context: Does it provide enough background information?
- Constraints: Are boundaries and rules clearly stated?
- Examples: Are there concrete examples of good output?
- Identify common issues:
- Vague verbs ("handle", "process", "manage") without specifics.
- Missing edge case guidance.
- No output format specification.
- Contradictory instructions.
- Missing success criteria.
- Rewrite the prompt with improvements:
- Add structured sections (Steps, Format, Rules).
- Replace vague instructions with specific actions.
- Add output format with examples.
- Define explicit constraints and error handling.
- Compare original vs improved versions side by side.
Format
Prompt Analysis:
Clarity: <1-5>/5
Specificity: <1-5>/5
Context: <1-5>/5
Issues found:
- <issue description>
Improved prompt:
<rewritten prompt>
Changes made:
- <what was improved and why>
Rules
- Preserve the original intent; only improve clarity and structure.
- Use imperative mood for instructions ("Run X" not "You should run X").
- Every prompt should have Steps, Format, and Rules sections.
- Limit prompts to under 50 lines; split complex workflows into sub-commands.
- Test the improved prompt against the original to verify better results.
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.
- 6d ago First seen · 55 lines · 19 tokens per session scan A 40e49714fc02
improve-prompt is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,587 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 384 once invoked, about $0.0001 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-30.
Other commands, from other repositories
create-meta-prompt
Create optimized prompts for Claude-to-Claude pipelines (research -> plan -> implement).
apply-thinking-to
You are an expert prompt engineering specialist with deep expertise in applying Anthropic's extended thinking patterns to enhance prompt effectiveness. Your role is to systematically transform prompts using advanced reasoning frameworks to dramatically improve their analytical depth, accuracy, and reliability.
prompt-history
Manage history of created and optimized prompts.
prompt-test
Test LLM prompts against sample inputs. Shows outputs, checks for regressions when prompts change, and compares different prompt versions side-by-side.
t00-ai-dev
AI 应用开发模式 — Use when building AI apps, RAG, LLM applications, Claude API, or prompt engineering.
prompt-optimizer
Analyze and rewrite a prompt to maximize clarity, specificity, and output quality.