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 KaimingWan/oh-my-kiro --skill omk-skill-creationgit clone --depth 1 https://github.com/KaimingWan/oh-my-kiroWrote 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/kaimingwan/oh-my-kiro/omk-skill-creation)<a href="https://agentmods.dev/skills/kaimingwan/oh-my-kiro/omk-skill-creation"><img src="https://agentmods.dev/badge/skills/kaimingwan/oh-my-kiro/omk-skill-creation/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/kaimingwan/oh-my-kiro/omk-skill-creation"><img src="https://agentmods.dev/badge/skills/kaimingwan/oh-my-kiro/omk-skill-creation.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.00072 | $0.01933 |
| Opus 5 | $0.00036 | $0.00966 |
| Sonnet 5 | $0.00014 | $0.00387 |
| Haiku 4.5 | $0.00007 | $0.00193 |
Grade A, and why
omk-skill-creation 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 12d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creation — From Idea to Production
Trigger Examples
- "把这个重复流程做成 skill"
- "create a new skill for code review"
- "帮我写一个 SEO 研究的 skill"
- "review and improve this skill"
- "这个工作流应该 skillify"
Philosophy
Context window is a public good. Only add what the agent doesn't already know.
A skill is an onboarding manual for the agent — after reading it, the agent knows your process, standards, and preferences without re-teaching every session.
Phase 0: Should This Be a Skill?
Before writing anything, decide the right mechanism:
| Signal | Mechanism |
|---|---|
| Rule needed in EVERY conversation | AGENTS.md / rules.md |
| Must run automatically on events | Hook (gate/ or feedback/) |
| Teaches agent a specific workflow | Skill ← you are here |
| Gives agent a new tool/API | MCP server |
| Needs isolated context execution | Subagent |
Skill ROI threshold: Will this workflow run ≥3 times? If not, just explain in conversation.
Phase 1: Design (Before Writing SKILL.md)
Step 1: Define Use Cases
Write 3-5 concrete user prompts that should trigger this skill. Not abstract descriptions — actual sentences users will type:
Example for a "daily planning" skill:
- "plan my day"
- "start work"
- "今天做什么？"
- "morning routine"
- "daily standup prep"
These prompts shape everything: skill name, description, input/output, workflow steps.
Step 2: Define Input → Output
| Question | Answer |
|---|---|
| What does the user provide? | (file, URL, text, nothing?) |
| What does the skill produce? | (file, report, action, decision?) |
| What format? | (markdown, JSON, email, code?) |
Step 3: Choose Pattern
| Need external APIs/real-time data? | → Pattern C: Skill + MCP |
|---|---|
| Need deterministic computation? | → Pattern B: Prompt + Scripts |
| Agent judgment alone is enough? | → Pattern A: Prompt-Only |
When in doubt, start with Pattern A. Add scripts later if needed.
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.
- 12d ago First seen · 217 lines · 72 tokens per session scan A c6366bda4393
omk-skill-creation is a skill published in the GitHub repository KaimingWan/oh-my-kiro (103 stars, last pushed 5mo ago), licensed MIT. It adds 72 tokens to every session and 1,933 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…