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 agentmods add skills/kilo-org/kilocode/icon-vscodenpx skills add Kilo-Org/kilocode --skill icon-vscodegit 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/icon-vscode)<a href="https://agentmods.dev/skills/kilo-org/kilocode/icon-vscode"><img src="https://agentmods.dev/badge/skills/kilo-org/kilocode/icon-vscode.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 | $0.00024 | $0.01562 |
| Opus 5 | $0.00012 | $0.00781 |
| Sonnet 5 | $0.00005 | $0.00312 |
| Haiku 4.5 | $0.00002 | $0.00156 |
Grade A, and why
icon-vscode 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 5d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VS Code Icons
Use this skill for icon work in packages/kilo-vscode/, packages/kilo-ui/, and the shared packages/ui/ icon registry. Keep official VS Code workbench rules separate from Kilo's webview design system.
Choose the icon system first
| Surface | Use | Source of truth | Theme handling |
|---|---|---|---|
| VS Code commands, menus, and editor actions | Codicon, for example $(add), or a 16x16 single-color SVG only when needed |
packages/kilo-vscode/package.json records usages; VS Code command icons defines the contract |
VS Code themes Codicons; SVGs use light/dark contribution fields |
| Activity bar and view containers | 24x24 centered single-color icon by the VS Code convention; existing Kilo branding is an intentional asset exception | packages/kilo-vscode/package.json, packages/kilo-vscode/assets/icons/ |
Follow the contribution point; do not redesign the existing brand mark |
| Marketplace and extension branding | Packaged brand asset | packages/kilo-vscode/package.json, packages/kilo-vscode/assets/icons/ |
Existing Kilo assets define their own palette and variants |
| Webview buttons and UI | Icon or IconButton from @kilocode/kilo-ui |
packages/kilo-ui/src/components/icon.tsx, then packages/ui/src/components/icon.tsx |
currentColor and the VS Code theme bridge |
| Extension-contributed product icon | Existing WOFF2 font entry, for example $(kilo-logo) |
contributes.icons in packages/kilo-vscode/package.json and its usages |
VS Code product-icon theming |
Do not draw a custom SVG when an appropriate Codicon or existing registry icon already exists. Do not use a webview icon directly in package.json, or a VS Code contribution icon directly in the webview.
Existing repository conventions
- Search
packages/kilo-ui/src/components/icon.tsxfirst for Kilo-only icons, thenpackages/ui/src/components/icon.tsxfor shared icons. Preserve the existing key spelling, which is mostly kebab-case, and match a visual sibling before adding a new one. - Webview registry icons are inline SVG path strings, not standalone files. They use
fill="currentColor"orstroke="currentColor"; do not add theme duplicates or literal palettes to registry entries. Standalone brand artwork may use light/dark variants. - Match the closest registry sibling's
viewBox. The shared set is mostly20 20, with existing16 16entries; Kilo-only entries also intentionally use24 24. Icons render at 16px (small), 20px (normal), or 24px (medium/large). Never paste a path onto a different canvas without rebalancing it. - The extension's current brand assets are
kilo-light.svg,kilo-dark.svg,kilo-light.png,kilo-dark.png, andlogo-outline-black.png. The WOFF2 file is a packaged contribution font, not an editable icon source. - Registry icons are decorative by default. Icon buttons need an
aria-labelor visible button text; a tooltip or arbitrarylabelattribute is not sufficient unless the wrapper maps it to an accessible name.
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.
- 5d ago First seen · 64 lines · 24 tokens per session scan A 8c6e4c47396f
icon-vscode is a skill published in the GitHub repository Kilo-Org/kilocode (27,179 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 1,562 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 skills, from other repositories
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
openspec-continue-change
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.