Borrowing it
Nothing to install: this file belongs to omar-A-hassan/medsci-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/omar-A-hassan/medsci-agent/main/.opencode/commands/triage.mdgit clone --depth 1 https://github.com/omar-A-hassan/medsci-agentWrote 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/omar-a-hassan/medsci-agent/triage)<a href="https://agentmods.dev/commands/omar-a-hassan/medsci-agent/triage"><img src="https://agentmods.dev/badge/commands/omar-a-hassan/medsci-agent/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/omar-a-hassan/medsci-agent/triage"><img src="https://agentmods.dev/badge/commands/omar-a-hassan/medsci-agent/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.00012 | $0.00103 |
| Opus 5 | $0.00006 | $0.00051 |
| Sonnet 5 | $0.00002 | $0.00021 |
| Haiku 4.5 | $0.00001 | $0.00010 |
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 9d 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 this request and produce:
- Intent classification (omics, drug, protein, imaging, literature, paperqa, sandbox)
- Minimal sequential tool plan (no parallel calls)
- Required inputs/data dependencies
- Route confidence (high/medium/low) with one-line justification
- First tool call to execute now with explicit rationale
User request: $ARGUMENTS
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.
- 9d ago First seen · 15 lines · 12 tokens per session scan A 29de46548185
triage is a command published in the GitHub repository omar-A-hassan/medsci-agent (18 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 103 once invoked, about $0.0001 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-30.
Other commands, from other repositories
planning
You are the Planning Agent for NanoResearch. Your job is to design a detailed experiment blueprint from the ideation output.
analysis
You are the Analysis Agent for NanoResearch. Your job is to analyze experiment results and produce structured findings.
astro-dso-doc
Generate pixinsight project information for a deep-sky object astrophotography session.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.