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/new1direction/korgex/issue-triagenpx skills add New1Direction/korgex --skill issue-triagegit clone --depth 1 https://github.com/New1Direction/korgexWrote 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/new1direction/korgex/issue-triage)<a href="https://agentmods.dev/skills/new1direction/korgex/issue-triage"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/issue-triage.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.1 | $0.00018 | $0.00335 |
| Opus 5 | $0.00009 | $0.00168 |
| Sonnet 5 | $0.00004 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
issue-triage 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 6d 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
A good issue is half the fix. Whether filing or triaging, drive toward a crisp, reproducible statement of the problem.
- Reproduce or get repro steps. The most valuable thing in any bug report is a minimal, deterministic way to trigger it. If you can't reproduce it, say what you tried and what info is still needed — don't guess at a fix.
- Capture the essentials: exact steps, expected vs actual, environment (version, OS, config), and the actual error/output (not a paraphrase).
- Classify: is it a bug, a feature request, a question, or a duplicate? Search existing issues first — link duplicates instead of forking the discussion.
- Prioritize by impact × frequency. Severity (data loss / crash / cosmetic) and how many users hit it. Be honest; not everything is P0.
- Make it actionable. A triaged issue should tell the implementer where to look and how to know it's fixed (the repro becomes the acceptance test).
- For a fix you implement, reference the issue, and add a regression test from its repro so it can't silently come back (see test-driven-development).
Red flag: "it's broken" with no repro, version, or expected behaviour — that's not yet an issue, it's a prompt to gather more.
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.
- 6d ago First seen · 27 lines · 18 tokens per session scan A 78ec174f5513
issue-triage is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 335 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-31.
Other skills, from other repositories
vibe-bug-tracker
Use this skill to record production issues and maintain the historical bug list.
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
rust-check
Run cargo check on the current Rust project to find compile errors.
debug
Reproduce, minimize, localize, identify root cause, and distinguish diagnosis from an authorized fix. Prefer root-cause over symptom patches.