getkimchi/kimchi is a terminal-based coding agent that helps with software development through Kimchi’s language-model infrastructure. It can run tasks with one selected model or coordinate multiple models, with model roles chosen by its orchestration system.
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 getkimchi/kimchi --skill create-skillgit clone --depth 1 https://github.com/getkimchi/kimchiWrote 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/getkimchi/kimchi/create-skill)<a href="https://agentmods.dev/skills/getkimchi/kimchi/create-skill"><img src="https://agentmods.dev/badge/skills/getkimchi/kimchi/create-skill/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/getkimchi/kimchi/create-skill"><img src="https://agentmods.dev/badge/skills/getkimchi/kimchi/create-skill.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.00015 | $0.00985 |
| Opus 5.5 | $0.00006 | $0.00394 |
| Sonnet 5.5 | $0.00003 | $0.00197 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
create-skill 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 29d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a skill
Turn the user's workflow into a skill Kimchi can reuse. Use plain language: a skill is a folder containing instructions and any scripts, references, or assets needed for the workflow.
1. Define the workflow
First, check whether the user's request or conversation identifies the workflow. If the user invokes this skill without a purpose, ask one short question about the work they want to repeat, then stop and wait for their answer. Do not inspect files, Git history, or other skills to guess the purpose.
Once the purpose is clear, identify what the skill should do, when to use it, the inputs it needs, and what a good result looks like. This can be a business task (meeting notes, customer updates, report preparation) or a technical task. Ask only for information that would change the result; do not make the user fill out a technical template.
Inspect an existing skill before updating it. Reuse a matching skill instead of creating a duplicate, and preserve unrelated instructions and supporting files.
2. Choose where to save
Honor an explicit destination and any workspace instructions. Otherwise ask whether the skill is for this project or for all the user's projects, explaining the choice without requiring a path:
- This project:
.kimchi/skills/<name>/SKILL.mdin the project root. Project skills load only after the folder is trusted. - All projects:
~/.config/kimchi/harness/skills/<name>/SKILL.md.
Do not choose another harness's skills directory merely because it exists; Kimchi may not be configured to load it. Check for a same-name skill before writing; update it only when that is the requested intent, otherwise choose a distinct name. Do not write into this bundled skill's directory or a temporary discovery copy.
3. Write the instructions
Create a folder named after the skill and a SKILL.md with YAML frontmatter:
name: 1–64 lowercase letters, digits, or hyphens, with no leading, trailing, or consecutive hyphens.description: a nonempty string of at most 1024 characters explaining the task and when to use it. Quote descriptions containing YAML punctuation such as a colon followed by a space.
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.
- 29d ago First seen · 61 lines · 15 tokens per session scan A 5b48b5470fe2
create-skill is a skill published in the GitHub repository getkimchi/kimchi (2,276 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 985 once invoked, about $0.0001 per session on Opus 5.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-26.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.