Kilo Code is an open-source AI coding agent that works inside VS Code and JetBrains, from the command line, or through cloud services. Developers use it to build software with AI models, switch between providers, and run cloud agents or automated code reviews. The catalogue includes eleven skills, eight agents, and one instruction for Kilo Code.
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 Kilo-Org/kilocode --skill jetbrains-devgit clone --depth 1 https://github.com/Kilo-Org/kilocodeWrote 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/kilo-org/kilocode/jetbrains-dev)<a href="https://agentmods.dev/skills/kilo-org/kilocode/jetbrains-dev"><img src="https://agentmods.dev/badge/skills/kilo-org/kilocode/jetbrains-dev/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/kilo-org/kilocode/jetbrains-dev"><img src="https://agentmods.dev/badge/skills/kilo-org/kilocode/jetbrains-dev.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.00052 | $0.02668 |
| Opus 5.5 | $0.00021 | $0.01067 |
| Sonnet 5.5 | $0.00010 | $0.00534 |
| Haiku 4.5 | $0.00005 | $0.00267 |
Grade A, and why
jetbrains-dev 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 17d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JetBrains Plugin Build, Run, and Debug
Detailed reference for building, running, and debugging packages/kilo-jetbrains/. See packages/kilo-jetbrains/AGENTS.md for the always-on restrictions and key command summary; this skill covers the full workflow.
CLI Integration
- CLI process spawning, download, extraction, and lifecycle belong in
backend. - By default, the plugin does not bundle CLI binaries. At connect time the backend downloads the GitHub Release asset for the version pinned in
packages/kilo-jetbrains/package.json;backendresources includekilo.propertieswithcli.versionandcli.pinnedfor split-mode RPC and runtime use. - Bundled release builds pass
-Pkilo.cli.bundled=truewhile keepingkilo.cli.pinned=true. This build-only flag stages all pinned CLI release assets intokilo-cli.zip; runtime detects that resource and extracts only the current platform instead of downloading. Do not add acli.bundledkey tokilo.propertiesor repurposekilo.cli.pinned=falsefor public bundled releases. - For release questions, use the
/release-jetbrainscommand; it verifies the CLI pin before creating immutablejetbrains/v*tags. - For OS and environment checks, prefer IntelliJ Platform classes over raw JVM APIs such as
System.getProperty(...)orSystem.getenv(...). - Detect architecture with
com.intellij.util.system.CpuArch.CURRENT, notSystem.getProperty("os.arch"). - Detect OS with
com.intellij.openapi.util.SystemInfo.isMac/isLinux/isWindows. - Read environment variables with
com.intellij.util.EnvironmentUtil.getValue(...)orgetEnvironmentMap()when platform-aware environment handling matters. - Resolve IDE paths with
com.intellij.openapi.application.PathManagerrather than inferring paths from process working directories. - For packaging/build plumbing, see
script/build.tsandbackend/build.gradle.kts.
CLI Pinning, Unpinning, and Bumping
The JetBrains plugin has two independent CLI controls. Use the commands below directly when asked to change either one; do not hand-edit versions by guesswork.
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.
- 17d ago First seen · 85 lines · 52 tokens per session scan A d485b4ade458
jetbrains-dev is a skill published in the GitHub repository Kilo-Org/kilocode (27,622 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 2,668 once invoked, about $0.0002 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-29.
Other skills, from other repositories
issue
You are a senior engineering lead and product architect. Given an observation, bug, or gap, conduct a thorough multi-dimensional investigation, find the root cause, plan the resolution, and create a detailed actionable GitHub issue.
fix-bugs
Autonomously fix bugs from any source — Slack threads, failing CI tests, docker logs, or a plain description. Use when you have a bug report or failing test and want Claude to investigate and fix without step-by-step guidance.
rel-ai-debugging
Use when repository behavior is reproducibly wrong and needs causal diagnosis or repair, including errors, broken tests, crashes, regressions, failed contracts, or incorrect runtime behavior. Do not use for general audits or final verification when no active defect is being diagnosed.
rel-ai-investigation
Use for read-only repository questions that need evidence, including architecture audits, feasibility studies, dependency or caller tracing, impact analysis, implementation-status checks, and proof of how something works. Do not use to implement fixes or for final completion or release verification of changes already…
codebase-insight
When the user wants to deeply understand a codebase, map its architecture, or build a persistent mental model for future sessions. Use when the user says "explain this codebase," "map the architecture," "codebase insight," "understand this repo," "what does this project do," "how does this work," "analyze the…
bughunter
When the user wants to find bugs, test edge cases, stress-test code, or perform adversarial analysis of their codebase. Use when the user says "find bugs," "break this," "what could go wrong," "red team," "hunt bugs," "adversarial test," "edge cases," "stress test," "what did I miss," "pen test this logic," or before…