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.
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWrote 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/nodnarbnitram/claude-code-extensions/triage)<a href="https://agentmods.dev/commands/nodnarbnitram/claude-code-extensions/triage"><img src="https://agentmods.dev/badge/commands/nodnarbnitram/claude-code-extensions/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/commands/nodnarbnitram/claude-code-extensions/triage"><img src="https://agentmods.dev/badge/commands/nodnarbnitram/claude-code-extensions/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.00011 | $0.00385 |
| Opus 5.5 | $0.00004 | $0.00154 |
| Sonnet 5.5 | $0.00002 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
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.
What it actually says
Linear Triage Workflow
You are initiating a triage workflow. Your job is to gather information and then activate the linear skill.
Input Provided
Arguments: $ARGUMENTS
Step 1: Parse Arguments
Check if arguments include:
- Issue description (required)
- Team identifier (optional, e.g.,
--team IAI)
If no team is specified, default to IAI.
Step 2: Gather Missing Information
If the issue description is unclear or missing details, use AskUserQuestion to clarify:
- What is the issue or feature being triaged?
- What is the priority? (1=urgent, 2=high, 3=medium, 4=low)
- Any specific labels to apply?
Step 3: Confirm Details
Before proceeding, confirm with the user:
Issue: [parsed description] Team: [team identifier] Priority: [if specified]
Step 4: Activate Skill
Once you have all the information, invoke the linear skill and tell it to create a ticket using the wrapper scripts.
"Use the linear skill to create a Linear ticket for: [issue description] in team [team], with priority [priority] and labels [labels if any]."
The linear skill should be the source of truth for ticket creation and ticket lookup. After ticket creation, the agent can continue with branch, proposal, commit, and PR workflows as needed.
Example Usage
/triage Users can't log in with SSO
/triage Add dark mode support --team IAI
/triage Fix payment timeout --team ICE
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 · 54 lines · 11 tokens per session scan A 4d534834ec09
triage is a command published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 385 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.