Borrowing it
Nothing to install: this file belongs to jayminwest/kotadb. 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/jayminwest/kotadb/develop/.claude/commands/issues/classify_issue.mdgit clone --depth 1 https://github.com/jayminwest/kotadbWrote 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/jayminwest/kotadb/classify_issue)<a href="https://agentmods.dev/commands/jayminwest/kotadb/classify_issue"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/classify_issue/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/jayminwest/kotadb/classify_issue"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/classify_issue.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.00000 | $0.00267 |
| Opus 5.5 | $0.00000 | $0.00107 |
| Sonnet 5.5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
classify_issue 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.
What it actually says
/classify_issue
Template Category: Message-Only
Based on the GitHub issue payload below, choose the correct slash command. Respond with exactly one token: /feature, /bug, /chore, or 0 if none apply.
Guidance
/feature: net-new capability or enhancement delivering user value./bug: incorrect behaviour, regressions, failing tests, or outages./chore: maintenance, refactors, dependency upgrades, tooling changes, docs-only work.0: insufficient info or out-of-scope for automation.
Think carefully about impact, urgency, and deliverables described in the issue before answering.
Output Schema
The output must match this pattern:
- Type: string
- Enum:
/feature,/bug,/chore,0 - Format: Single line, no whitespace, no explanatory text
Correct outputs:
/feature
/bug
/chore
0
INCORRECT outputs (do NOT do this):
This issue should be classified as: /feature
Based on the issue description, I recommend /chore
GitHub Issue
$ARGUMENTS
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 · 47 lines · 0 tokens per session scan A b6147aa60781
classify_issue is a command published in the GitHub repository jayminwest/kotadb (100 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 267 tokens. 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 commands, from other repositories
sprint
Équipe de Développement Sprint - Implémentation parallèle de stories utilisant les Agent Teams.
workflow-design
Exécuter la phase de Conception (Solutioning) - générer la spécification technique (défaut) ou la constitution du projet (--constitution).
speckit.companion.implement
Companion implement — execute tasks.md in dependency order, then mark complete.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
speckit.companion.living-move
Move a living spec between central and colocated storage — file, tiers, and registry together (opt-in, reversible).
camp-init
Create a new camp with the standard directory structure. A camp was previously called a campaign; camp init is the same command either way.