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/zyrexnn/cybermes/triagegit clone --depth 1 https://github.com/Zyrexnn/CybermesWrote 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/zyrexnn/cybermes/triage)<a href="https://agentmods.dev/commands/zyrexnn/cybermes/triage"><img src="https://agentmods.dev/badge/commands/zyrexnn/cybermes/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 | $0.00000 | $0.00837 |
| Opus 5 | $0.00000 | $0.00418 |
| Sonnet 5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00084 |
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 4d 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.
This is a copy
100% identical to triage — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: triage description: Quick 7-Question Gate triage on a finding before writing a report. Kills N/A submissions before they happen. Faster than /validate — for quick go/no-go decisions. Usage: /triage
/triage
Quick triage to decide: submit or kill?
When to Use
Use this before spending time writing a full report. If triage passes, run /validate for the full 4-gate check, then /report.
Usage
/triage
Describe the finding in one sentence. Example:
- "I can read other users' orders by changing user_id in /api/orders/{id}"
- "The /api/export endpoint returns 200 with data even with no auth header"
- "I found X-Forwarded-Host is reflected in the password reset email"
The 7 Questions (Fast Version)
Answer YES or NO to each. First NO = kill it immediately.
Q1: Can I demonstrate this with a real HTTP request RIGHT NOW?
YES: I have the request/response already
NO: I need to look at more code first → KILL
Q2: Is this impact type accepted by the program?
YES: Bug class is on their accepted list
NO: They explicitly exclude this type → KILL
Q3: Is the vulnerable asset owned by and in scope for the program?
YES: Domain confirmed in-scope, not third-party
NO: Third-party service or excluded domain → KILL
Q4: Does this work without admin/privileged access?
YES: Regular user account is enough
NO: Requires admin → KILL (99% of programs)
Q5: Is this NOT already known/disclosed/documented behavior?
YES: Not in changelogs, not in disclosed reports
NO: It's documented as intended → KILL
Q6: Can I prove impact beyond "technically possible"?
YES: I have actual data in the response / action completed
NO: I only have a 200 status or error message → DOWNGRADE
Q7: Is this NOT on the never-submit list?
YES: It's a real bug class
NO: Missing headers, self-XSS, open redirect alone, etc. → KILL or CHAIN
Fast Kill Checklist
Kill immediately if ANY of these are true:
[ ] "Admin can do X" = not a bug
[ ] "Could theoretically lead to..." = no PoC = not a bug
[ ] Bug requires 3+ preconditions simultaneously
[ ] Finding is a missing header, missing flag, missing DMARC
[ ] SSRF with DNS callback only, no data returned
[ ] Open redirect with no OAuth chain or ATO path
[ ] Self-XSS (only affects your own account)
[ ] Introspection only (no IDOR, no auth bypass shown)
[ ] Rate limit on login/contact/search (Cloudflare covers 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.
- 4d ago First seen · 97 lines · 0 tokens per session scan A c319f357f434
triage is a command published in the GitHub repository Zyrexnn/Cybermes (668 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 837 tokens. A static security scan graded it A with 0 findings. It is 100% identical to triage, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
aod.deliver
Close a completed feature with automatic documentation updates and cleanup (Triad-enhanced).
aod.project-plan
Create implementation plan with dual sign-off (PM + Architect) - Streamlined v2.
aod.roadmap
Scaffold a quarterly roadmap document from completed PRDs with PM sign-off.
aod.score
Re-score an existing idea's ICE rating when circumstances change.
sicario.assess
Assess the repository against SicarioSpec guardrails.
sicario.review
Review the active spec, plan, tasks, staged changes, or branch for security and governance gaps.