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 terrene-foundation/kailash-coc-claude-py --skill issue-triage-routinggit clone --depth 1 https://github.com/terrene-foundation/kailash-coc-claude-pyWrote 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/terrene-foundation/kailash-coc-claude-py/issue-triage-routing)<a href="https://agentmods.dev/skills/terrene-foundation/kailash-coc-claude-py/issue-triage-routing"><img src="https://agentmods.dev/badge/skills/terrene-foundation/kailash-coc-claude-py/issue-triage-routing/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/terrene-foundation/kailash-coc-claude-py/issue-triage-routing"><img src="https://agentmods.dev/badge/skills/terrene-foundation/kailash-coc-claude-py/issue-triage-routing.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.00051 | $0.02101 |
| Opus 5 | $0.00026 | $0.01051 |
| Sonnet 5 | $0.00010 | $0.00420 |
| Haiku 4.5 | $0.00005 | $0.00210 |
Grade A, and why
issue-triage-routing 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 9d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage → Upflow Routing — Depth Reference
The always-on routing MUST lives in rules/issue-triage-routing.md (read
.claude/VERSION::type → route by class). This skill carries the on-demand
depth: how each repo class routes, the two upflow paths (Route-A issue vs the
Step-7c PR), the origination taxonomy, and why the durable surface is always
the proposal — never a local artifact edit. The authoritative mechanics live in
rules/artifact-flow.md § "Issue Routing By Change Type"; this skill is the
triage-time companion that resolves the class → lane decision.
The Discriminator: Route By Change TYPE, Not Repo Convenience
Every artifact-or-code issue routes by the TYPE of change it requests:
- COC-artifact improvement (method, rules, skills, agents, COC-tooling) →
the USE-template lane → a proposal via
/codifyStep 7b. - Bug / code / feature / code-improvement (SDK code) → the BUILD lane →
cross-SDK FIRST, then a proposal via
/codifyStep 7a.
Routing by repo convenience (a COC-method fix filed on BUILD; an SDK bug filed on a USE template) puts the change on the wrong lane — it never becomes the right kind of proposal, and the Gate-1 global-vs-variant split is bypassed.
The Four Repo Classes (read .claude/VERSION::type)
type |
Role | A triaged issue routes to… |
|---|---|---|
coc-use-template |
origination node | /codify Step 7b proposal → loom /sync-from-use Gate-1 → /sync-to-use redistributes |
coc-project |
downstream consumer | UP to the template pulled from: /codify Step 7c PR to the template inbox (primary), or Route-A issue (fallback) |
coc-build |
SDK code | cross-SDK FIRST → /codify Step 7a proposal |
coc-source |
loom (splitter) | INGEST via /sync-from-build + /sync-from-use, Gate-1 classify — never originate a local artifact |
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.
- 9d ago First seen · 135 lines · 51 tokens per session scan A 8b799ec76b9b
issue-triage-routing is a skill published in the GitHub repository terrene-foundation/kailash-coc-claude-py (12 stars, last pushed 24d ago), licensed Apache-2.0. It adds 51 tokens to every session and 2,101 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-09-03.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.