Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add testdouble/han/plugin install han-researchWrote 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/testdouble/han/issue-triage)<a href="https://agentmods.dev/skills/testdouble/han/issue-triage"><img src="https://agentmods.dev/badge/skills/testdouble/han/issue-triage/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/testdouble/han/issue-triage"><img src="https://agentmods.dev/badge/skills/testdouble/han/issue-triage.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.00106 | $0.02377 |
| Opus 5.5 | $0.00042 | $0.00951 |
| Sonnet 5.5 | $0.00021 | $0.00475 |
| Haiku 4.5 | $0.00011 | $0.00238 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context
- CLAUDE.md: !
find . -maxdepth 1 -name "CLAUDE.md" -type f - project-discovery.md: !
find . -maxdepth 3 -name "project-discovery.md" -type f - personal config directory: !
bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude" - project .han/config.md: !
cat .han/config.md 2>/dev/null || echo ""
As your first action, use the Read tool on .han/config.md inside the personal config directory path above. A read
that returns no file is no personal configuration: continue silently. When that file or the project .han/config.md
probe supplies content, apply it per config-rule.md, which governs precedence
between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.
Triage Approach
- Work only from what the reporter wrote. Do not infer facts that are not stated. This is the single most important constraint in this skill.
- Classify the issue type before doing anything else. The type drives what counts as missing information.
- Severity and reproducibility are estimates based on what is known. For a Bug, Regression, Performance, or Security issue, mark them Unknown when not inferable. For a Feature Request, Question, or Other issue, omit them entirely when they are not inferable (see Step 4) rather than rendering Unknown.
- The recommended next step is the single most appropriate han skill (or "clarify with reporter") to run after triage completes.
- Project context (CLAUDE.md, project-discovery.md) is read only to identify Suspected Areas. Never use it to supply information the reporter omitted.
- Source the standard by invoking
han-communication:readability-guidanceand apply it as you write the triage document. Hold its default audience frame: a capable reader who did not do this work and lacks the author's context.
Issue Triage
Step 0: Resolve the Issue Text
Determine the issue text from the argument:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 168 lines · 106 tokens per session scan A 05371ce345ff
issue-triage is a skill published in the GitHub repository testdouble/han (316 stars, last pushed 3d ago), licensed MIT. It adds 106 tokens to every session and 2,377 once invoked, about $0.0004 per session on Opus 5.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
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
deadeye-sweep
Applies the findings from /deadeye-review, /deadeye-pr, and /deadeye-guard, verifies the build, and re-scans on a loop until nothing (critical/high, or every severity with --all) survives. In --pr mode also answers the PR's own open review comments, replying and resolving.
lsp-investigate
Investigate code using LSP tools. Register a project, then use definitions, references, call hierarchies, type hierarchies, hover, and diagnostics to understand code structure, trace bugs, and assess change impact.
verify-simplify
A final code-cleanup workflow that runs at the end of verification. It removes repeated or unnecessary logic after the other verification steps are complete.
daily-prevention
Use this skill to help a developer keep day-to-day code simple, maintainable, and robust — through automatable prevention (linters, type checkers, static analysis, and — for what static analysis structurally can't catch — AI-assisted review skills) rather than after-the-fact fixes. Trigger on "how do I keep this…
vet
Thorough codebase investigation that finds and fixes real problems. Maps architecture, scans every layer (structural, correctness, security, reliability, performance, hygiene), prioritized report with evidence, fix plan, executes collaboratively. A senior engineer doing a full review with authority to fix. Use when…