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 agents/bcanfield/agentic-tech-debt/triage-labelsgit clone --depth 1 https://github.com/bcanfield/agentic-tech-debtWrote 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/agents/bcanfield/agentic-tech-debt/triage-labels)<a href="https://agentmods.dev/agents/bcanfield/agentic-tech-debt/triage-labels"><img src="https://agentmods.dev/badge/agents/bcanfield/agentic-tech-debt/triage-labels.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.00304 |
| Opus 5 | $0.00000 | $0.00152 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
triage-labels 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 4d 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 labels
Label vocabulary for triaging/grilling issues in this repository.
Managed by smallhours setup — edit .smallhours.yml labels: to rename,
then re-run setup; do not edit this file by hand.
needs-triage— State: awaiting triage/grillingneeds-info— State: blocked on missing informationready-for-agent— State: grilled + authorized; the loop's triggeragent-working— State: smallhours is implementing/fixing/resolvingin-review— State: PR ready; maintainer review is the only pending actready-for-human— State: needs a person, not the agentwontfix— State: will not be workedagent— PR: automation-owned; smallhours may modifyci-failing— PR: CI redready-to-merge— PR: green + CLEAN, ready for review/mergehuman-needed— PR: automation gave upbug— Category: something is brokenenhancement— Category: new capability or improvement
System-owned states
agent-working and in-review are applied and removed by the smallhours loop only.
Never hand-apply them during triage: removing or adding one by hand is
a signal to the system (cancellation / state drift), not bookkeeping.
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.
- 4d ago First seen · 26 lines · 0 tokens per session scan A 7cf535581b5c
triage-labels is an agent published in the GitHub repository bcanfield/agentic-tech-debt (8 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 304 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 agents, from other repositories
planner
Use when starting a new round (substrate-touching / fix-round / admin) to generate a complete handoff doc from scope + prior-round context. Replaces hand-written 18/12/10-section handoff docs.
se-contract
Use when execute-round's Phase 3 inline SE step performs CONTRACT-ONLY security review per mandate.
ba-designer
Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.
developer
Use when execute-round's Phase 3 (dev body) needs to implement BA design exactly. Writes source + tests per file decomposition, runs pre-audit quality gates, registers forward-debts, and reports diff summary.
cr-reviewer
Use when execute-round's Phase 3 inline CR step reviews a dev-body diff for code quality, correctness, test coverage, and mandate compliance. Produces P0/P1/P2/P3 findings table.
arcgentic-orchestrator
Top-level round driver. Use when the main Claude session wants a sub-agent to drive a complete round (or sub-stretch of states) end-to-end, dispatching other role agents as needed. Reads .agentic-rounds/state.yaml, advances state machine via transition.sh, dispatches sub-agents via Task tool when role-switching is…