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/gh-issuesnpx skills add Kilo-Org/kilocode --skill gh-issuesgit 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/gh-issues)<a href="https://agentmods.dev/skills/kilo-org/kilocode/gh-issues"><img src="https://agentmods.dev/badge/skills/kilo-org/kilocode/gh-issues.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.00050 | $0.00547 |
| Opus 5 | $0.00025 | $0.00273 |
| Sonnet 5 | $0.00010 | $0.00109 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
gh-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 4d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues
Use this skill whenever you create or manage a GitHub issue with gh for either the VS Code extension or the JetBrains plugin.
Templates
The repo defines issue templates in .github/ISSUE_TEMPLATE/. Pick the matching template instead of opening a blank issue:
| Template | When to use |
|---|---|
Bug report (bug-report.yml) |
Reproducible defects with steps, expected, and actual behavior |
Feature Request (feature-request.yml) |
New capabilities, enhancements, or behavior changes |
Question (question.yml) |
Usage or design questions that aren't obviously bugs or feature requests |
Pass the template title to gh issue create --template.
Title Conventions
- Use a plain, descriptive title that reads cleanly as a standalone sentence.
- Do not add platform-specific prefixes such as
[JetBrains],[Jetbrains],[JB],[VS Code],[VSCode], or similar. Routing happens through project boards, not the title.
Project Boards
Every new issue must land on the correct project board:
| Surface | Project | URL |
|---|---|---|
| VS Code extension | VS Code Extension |
https://github.com/orgs/Kilo-Org/projects/25 |
| JetBrains plugin | Jetbrains Plugin |
https://github.com/orgs/Kilo-Org/projects/39 |
Pass the project title to gh issue create --project.
Recipes
Create a VS Code extension bug report and add it to the board:
gh issue create \
--template "Bug report" \
--project "VS Code Extension" \
--title "Sidebar chat fails to render after reload" \
--body "..."
Create a JetBrains feature request:
gh issue create \
--template "Feature Request" \
--project "Jetbrains Plugin" \
--title "Support Kotlin Multiplatform target detection" \
--body "..."
Scope Errors
If gh reports a missing scope when assigning a project, refresh the auth token and retry:
gh auth refresh -s project
After the refresh succeeds, re-run the original gh issue create command. Do not fall back to creating the issue without the project — the board assignment is required.
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.
- 4d ago First seen · 69 lines · 50 tokens per session scan A ece0e38363fc
gh-issues is a skill published in the GitHub repository Kilo-Org/kilocode (27,119 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 547 once invoked, about $0.0003 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-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-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
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.