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/higoralves/orc/triagegit clone --depth 1 https://github.com/HigorAlves/orcWrote 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/higoralves/orc/triage)<a href="https://agentmods.dev/commands/higoralves/orc/triage"><img src="https://agentmods.dev/badge/commands/higoralves/orc/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.00046 | $0.02658 |
| Opus 5 | $0.00023 | $0.01329 |
| Sonnet 5 | $0.00009 | $0.00532 |
| Haiku 4.5 | $0.00005 | $0.00266 |
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 5d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orc:triage
Move issues on the project tracker through a small state machine of triage roles: categorise → verify the claim → grill if needed → write an agent-ready brief, park it, or reject it.
If the tracker config treats external pull requests as a request surface, triage covers them too: a PR is an issue with attached code — same roles, same states, same machine, with the PR deltas marked below. Resolve a bare #42 to an issue or PR per the tracker config.
Phase 0 — Read the tracker layer
Run the orc:tracker-config read protocol (issue-tracker.md + triage-labels.md). It owns the missing-config gate — one canonical ask, and a "use defaults" answer is recorded as a settled decision so no tracker-aware command re-asks this session.
Tracker dispatch:
- GitHub — issues and external PRs via
gh(orc:gh-cli). PRs are in discovery scope only when the config's "PRs as a request surface" flag isyes; an explicitly named PR is always triaged regardless. - Jira — work items via
acli(orc:jira-cli); triage state is applied as Jira labels pertriage-labels.md. External PRs, when in scope, are still read viagh. - Local markdown — edit the
Status:/Category:lines and## Commentssections in the issue files the config points at.
Also read docs/agents/domain.md and follow its consumer rules (glossary vocabulary, ADR awareness) for every codebase exploration below.
Roles
Two category roles — bug (something is broken) and enhancement (new feature or improvement) — and five state roles:
needs-triage— maintainer needs to evaluateneeds-info— waiting on reporter for more informationready-for-agent— fully specified, ready for an AFK agentready-for-human— needs human implementationwontfix— will not be actioned
For a PR the same states read against the attached code: ready-for-agent means a brief is attached and an agent should take the next step on the diff; ready-for-human means it's ready for a human to merge.
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.
- 5d ago First seen · 188 lines · 46 tokens per session scan A bfd76b6f4192
triage is a command published in the GitHub repository HigorAlves/orc (6 stars, last pushed 9d ago), licensed MIT. It adds 46 tokens to every session and 2,658 once invoked, about $0.0002 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 commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Manually trigger plan-sync to update downstream task specs after implementation drift.
setup
Set up Postman MCP Server. Authenticate via OAuth or API key, verify connection, select workspace.
uninstall
Remove flow-next files from project.
test
Run Postman collection tests, analyze results, diagnose failures, and suggest fixes.
refine-title
深度分析 Issue 或 PR 内容，并将其标题重构为 Conventional Commits 格式.