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.
Borrowing it
Nothing to install: this file belongs to Kilo-Org/kilocode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Kilo-Org/kilocode/main/.opencode/command/issues.mdgit 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/commands/kilo-org/kilocode/issues)<a href="https://agentmods.dev/commands/kilo-org/kilocode/issues"><img src="https://agentmods.dev/badge/commands/kilo-org/kilocode/issues/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/commands/kilo-org/kilocode/issues"><img src="https://agentmods.dev/badge/commands/kilo-org/kilocode/issues.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.00006 | $0.00123 |
| Opus 5.5 | $0.00002 | $0.00049 |
| Sonnet 5.5 | $0.00001 | $0.00025 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
issues 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 1mo 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.
This is a copy
88% identical to issues — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Search through existing issues in Kilo-Org/kilocode using the gh cli to find issues matching this query:
$ARGUMENTS
Consider:
- Similar titles or descriptions
- Same error messages or symptoms
- Related functionality or components
- Similar feature requests
Please list any matching issues with:
- Issue number and title
- Brief explanation of why it matches the query
- Link to the issue
If no clear matches are found, say so.
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.
- 1mo ago First seen · 24 lines · 6 tokens per session scan A 149008751e77
issues is a command published in the GitHub repository Kilo-Org/kilocode (27,710 stars, last pushed today), licensed MIT. It adds 6 tokens to every session and 123 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to issues, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
set-tracker
Set the issue tracker for the current project.
speckit.companion.implement
Companion implement — execute tasks.md in dependency order, then mark complete.
speckit.companion.living-move
Move a living spec between central and colocated storage — file, tiers, and registry together (opt-in, reversible).
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
orchestrate
You are the Project Orchestrator, the ultimate enforcer of the NASAB framework principles in all project workflows. You coordinate multi-agent work while ruthlessly enforcing quality gates, capability validation, and the principle of Patience (Pillar 6): perfect before advancing.