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/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/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/higoralves/orc/triage"><img src="https://agentmods.dev/badge/commands/higoralves/orc/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.00031 | $0.01400 |
| Opus 5.5 | $0.00012 | $0.00560 |
| Sonnet 5.5 | $0.00006 | $0.00280 |
| Haiku 4.5 | $0.00003 | $0.00140 |
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 2d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orc:triage
The intake for every incoming report: categorise it, check it is valid, grill when needed, then brief, file, park or reject it.
Arguments
<issue/PR number, Jira key, or natural-language request>— optional. A bare#42resolves to an issue or a PR per the tracker config.--sentry <id|url>— a Sentry issue short ID or URL. Read-only intake viaorc:triage/P4.<pasted report>— a chat message, email, stack trace or complaint with no tracker item. Intake viaorc:triage/P4.
Natural-language routing: "Show me anything that needs my attention" → P1; "Let's look at #42" or "look at PROJ-123" → P2; "Is this real?" plus a paste → P4; "Move #42 to ready-for-agent" → P3; "What's ready for agents to pick up?" → query and list.
Preconditions
🛑 Outward write
Every tracker write (label, comment, close) sits behind a
📋 Preview — tracker writesgate. It is hard-outward perorc:using-orc;--autoandinteraction_policynever skip it.
- The tracker layer must exist;
orc:tracker-configowns the missing-config gate (one canonical ask per session). - A "use defaults" answer is a settled decision: no tracker-aware command re-asks this session.
- A PR is an issue with attached code: same roles, states and machine. PR deltas:
orc:triage/P2,orc:triage/BRIEFS.
Phases
Modules live in orc:phases (references/triage/). Entering a phase, Read exactly its module.
| Phase | Module | Skipped when |
|---|---|---|
| 0 Detect context | resident, below | never |
| 1 Attention queue | orc:triage/P1 |
the request names an item or a state move |
| 2 Triage a specific item | orc:triage/P2 |
attention queue (until a pick) or quick override |
| 3 Quick state override | orc:triage/P3 |
the request is not "move X to " |
| 4 Intake a raw report | orc:triage/P4 |
the input is a tracker item |
| Validity check | orc:triage/VALIDITY |
never in P2 and P4 |
| Roles and transitions | orc:triage/ROLES |
the run writes no role |
| Briefs and triage notes | orc:triage/BRIEFS |
no brief or notes to post |
| Out-of-scope KB | orc:triage/OUT-OF-SCOPE |
never; P2 reads it, rejected enhancements write it |
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.
- 2d ago Changed · -83 lines · -15 tokens per session 66642ad4f834
- 1mo 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 yesterday), licensed MIT. It adds 31 tokens to every session and 1,400 once invoked, about $0.0001 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-31.
Other commands, from other repositories
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
scout-work
Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
dashboard
Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
status
Show current execution status with progress, dependencies, file ownership, and parallelization opportunities.