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/enihcam/opencode-webmcp/triage-labelsgit clone --depth 1 https://github.com/enihcam/opencode-webmcpWhat 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.00357 |
| Opus 5 | $0.00000 | $0.00179 |
| Sonnet 5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00036 |
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 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.
What it actually says
Triage Labels
The five canonical triage roles and their GitHub label strings:
| Role | Label | Purpose |
|---|---|---|
| Needs evaluation | needs-triage |
New issues land here. Maintainer needs to evaluate and route. |
| Needs info | needs-info |
Waiting on reporter to provide missing information. |
| Ready for agent | ready-for-agent |
Fully specified, AFK-ready. An agent can pick this up with no human context. |
| Ready for human | ready-for-human |
Needs human judgement or implementation. |
| Won't fix | wontfix |
Out of scope, declined, or will not be actioned. |
State machine
[new issue] → needs-triage
↓
┌─── needs-info ←── (re-opened)
↓
ready-for-agent → (agent picks up)
ready-for-human → (human picks up)
wontfix → (closed, out-of-scope.md)
Adding new labels
Create them via gh:
gh label create "needs-triage" --color "#e4e669" --description "Needs maintainer evaluation"
gh label create "needs-info" --color "#fbca04" --description "Waiting on reporter"
gh label create "ready-for-agent" --color "#0e8a16" --description "Fully specified, AI-ready"
gh label create "ready-for-human" --color "#0052cc" --description "Needs human judgement"
gh label create "wontfix" --color "#ffffff" --description "Will not be actioned"
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 First seen · 36 lines · 0 tokens per session scan A f7729681ae69
triage-labels is an agent published in the GitHub repository enihcam/opencode-webmcp (1 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 357 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
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
replay-agent
Build replay sequences for UI debugging, regression testing, and automation.
Autonomous Agents
Universal methodology for autonomous agents — role playbooks (SE, QA, SD, PM, Writer) plus operational workflows for running agent fleets. App-agnostic: works with any web application or codebase.
analyzer
You are the Analyzer agent for Founder Mode — Phase 7: Post-Run Analysis.
architect-gen
You are the Architecture Generator agent for Founder Mode — Phase 2.
synthesizer
You are the Synthesizer for the Architect evaluation system. You receive structured outputs from multiple evaluator agents and synthesize them into a unified evaluation with clear scores, actionable recommendations, and strategic direction.