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 commands/refo/claude-dev-helpers/triage-issuegit clone --depth 1 https://github.com/refo/claude-dev-helpersWrote 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/refo/claude-dev-helpers/triage-issue)<a href="https://agentmods.dev/commands/refo/claude-dev-helpers/triage-issue"><img src="https://agentmods.dev/badge/commands/refo/claude-dev-helpers/triage-issue.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.00000 | $0.00399 |
| Opus 5 | $0.00000 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
triage-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 3d 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
Triage Issue
Systematically investigate a bug, design a fix, and create a GitHub issue with TDD approach.
Workflow
1. Problem Capture
Ask the user: "What's the problem you're seeing?" Capture their description with minimal follow-up questions. Go with their initial report — interview comes next.
2. Exploration & Diagnosis
Use the Agent tool to deeply investigate the codebase:
- Where does the bug manifest? (which file, component, API endpoint)
- What is the involved code path?
- What is the root cause?
- Are there related patterns elsewhere?
Examine source files, tests, git history, error handling, and similar working code.
3. Fix Approach
Determine:
- The minimal change needed
- Which modules are affected
- What behaviors need verification
- Is this a regression? Missing feature? Design flaw?
4. TDD Fix Design
Create ordered RED-GREEN cycles. Each cycle is one vertical slice:
- RED: Write a test for one observable behavior
- GREEN: Minimal code to pass
- Repeat until the issue is fixed
Rules:
- Tests verify behavior through public interfaces, not implementation details
- One test at a time
- Each test should survive internal refactors
5. GitHub Issue Creation
Generate the issue automatically using gh issue create without requesting user review first.
Use this template:
# <Issue Title>
## Problem
<Description of the bug from the user's perspective>
## Root Cause
<What's happening in the code>
## Solution
A TDD fix with ordered RED-GREEN cycles.
### Cycle 1: <Title>
**Test**: <Description of what the test verifies>
**Implementation**: <Minimal code needed to pass>
### Cycle 2: <Title>
... (repeat for each cycle)
## Verification
- [ ] All tests pass
- [ ] Behavior is fixed
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.
- 3d ago First seen · 77 lines · 0 tokens per session scan A 26b280cd5bb1
triage-issue is a command published in the GitHub repository refo/claude-dev-helpers (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 399 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-31.
Other commands, from other repositories
tdd-refactor
TDDのRefactorフェーズを実行します。テストを通す実装が完了した後、コード品質の改善とリファクタリングを行います。.
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
spec-impl
Execute spec tasks using TDD methodology.
pm-auto-design2dev
設計レビューから実装完了まで完全自動化（設計レビュー→作業計画→TDD実装）.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.