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 skills add yugasun/aiops --skill triagegit clone --depth 1 https://github.com/yugasun/aiopsWrote 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/skills/yugasun/aiops/triage)<a href="https://agentmods.dev/skills/yugasun/aiops/triage"><img src="https://agentmods.dev/badge/skills/yugasun/aiops/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.00028 | $0.00479 |
| Opus 5 | $0.00014 | $0.00239 |
| Sonnet 5 | $0.00006 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
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 7d 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
State machine for issues (and external PRs if configured in docs/agents/issue-tracker.md). Every tracker comment starts with:
This was generated by AI during triage.
Run /aiops-setup if triage label mapping is missing.
Roles
Category: bug | enhancement
State: needs-triage | needs-info | ready-for-agent | ready-for-human | wontfix
One category + one state per item. Label strings may differ — use docs/agents/triage-labels.md.
Brief format: AGENT-BRIEF.md. Rejections KB: OUT-OF-SCOPE.md.
Invocation
Natural language: "what needs attention", "triage #42", "move #42 to ready-for-agent".
Show attention
Buckets (oldest first): unlabeled, needs-triage, needs-info with new reporter activity. Tag [PR] vs [issue] when PRs are in scope.
Triage one item
- Gather — body, comments, labels, diff (PR). Check
.out-of-scope/for prior rejections; search codebase for existing implementation. - Recommend category + state; wait for maintainer.
- Verify — reproduce bug or validate PR claims before grilling.
- Grill if needed —
/grilling+/domain-modeling, update CONTEXT/ADRs inline. - Apply outcome:
ready-for-agent/ready-for-human— post briefneeds-info— triage notes (established + questions for reporter)wontfix— already implemented (point to code) | rejected bug (close) | rejected enhancement (.out-of-scope/then close)
Quick override
"Move #N to ready-for-agent" — apply directly after confirm; skip grill unless brief missing.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 47 lines · 28 tokens per session scan A c23f68987d5c
triage is a skill published in the GitHub repository yugasun/aiops (4 stars, last pushed 18d ago), licensed Apache-2.0. It adds 28 tokens to every session and 479 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-31.
Other skills, from other repositories
hashiiiii-pull-request
Use this skill to create or edit a GitHub pull request with the repository template or the default structure.
hashiiiii-issues
Use this skill to create or edit GitHub issues with a consistent body structure.
spec-kitty-implement-review
Orchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state transitions, rejection cycles, arbiter escalation, and dependency-aware sequencing across all 13 supported coding agents. Triggers: "implement and review WPs", "run the implement-review loop"…
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
pr-review
Multi-dimensional review of a PR or feature branch in microsoft/win-dev-skills. Activate on "review my PR / changes / branch", "vet before pushing", "PR review", "is this ready to merge". Fans out parallel sub-agents over skill content, the skill-vs-tool boundary (solution hierarchy), tool correctness…
review
Adversarial senior review of the spec before any code is written. Constructs a skeptical reviewer whose authority comes from the codebase, §R research, and live best-practice — then tries to REFUTE the spec, not rubber-stamp it. Every finding cites evidence (file:line or source); unverifiable ones are flagged.…