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-kimi-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-kimi-prompts)<a href="https://agentmods.dev/skills/ichendev/prompt-optimizer-plugins/optimize-kimi-prompts"><img src="https://agentmods.dev/badge/skills/ichendev/prompt-optimizer-plugins/optimize-kimi-prompts.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.00125 | $0.01124 |
| Opus 5 | $0.00063 | $0.00562 |
| Sonnet 5 | $0.00025 | $0.00225 |
| Haiku 4.5 | $0.00013 | $0.00112 |
Grade A, and why
optimize-kimi-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 8d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimize Kimi Prompts
Turn rough ideas and existing prompt stacks into copy-ready Kimi prompts. Preserve the user's intent and hard constraints, ask for genuinely blocking information, and keep simple tasks simple.
Use the official basis
Read references/official-guidance.md when model-specific rationale or the longer checklist is needed. Treat its prose as a dated summary and its URL as the canonical source. Fetch the live Moonshot AI page before making claims about current models, API fields, context limits, availability, or pricing.
Follow the workflow
1. Capture the prompt contract
Identify:
- the intended user-visible outcome and audience;
- the inputs, background, and reference text Kimi will receive;
- facts and constraints that must be preserved;
- the required output content, structure, language, and approximate length;
- evidence, tools, or validation needed for success;
- fallback behavior when an answer is absent from the supplied material.
Treat these as diagnostic dimensions, not mandatory headings. Preserve system, developer, user, and tool-description boundaries when the user supplies a layered prompt stack.
2. Apply the clarity gate
Ask a question only when two reasonable answers would materially change the outcome, source boundary, permissions, schema, or success criteria.
Treat these gaps as blocking by default:
- a vague topic and generic verb with no identifiable deliverable or audience;
- an unspecified source or reference set whose choice changes the answer;
- an external or irreversible action without an authorization boundary;
- conflicting requirements or an undefined strict output schema.
When clarification is blocking, ask one to three high-information questions and do not produce a provisional optimized prompt. Otherwise, proceed with conservative local assumptions and list only assumptions actually made. Never invent facts, sources, policies, access, or permissions.
3. Rewrite for Kimi
What ships with it
2 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.
- 8d ago First seen · 88 lines · 125 tokens per session scan A dce9dc9313d3
optimize-kimi-prompts is a skill published in the GitHub repository IchenDEV/prompt-optimizer-plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 125 tokens to every session and 1,124 once invoked, about $0.0006 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.
gpt-5-6-prompt-engine
Use when creating, auditing, rewriting, debugging, migrating, or evaluating GPT-5.6 Sol, Terra, or Luna prompt layers, tool descriptions, agent briefs, or prompt stacks; choosing runtime configuration; or comparing controlled prompt candidates.