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 skills/drvoss/everything-copilot-cli/triagenpx skills add drvoss/everything-copilot-cli --skill triagegit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWrote 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/drvoss/everything-copilot-cli/triage)<a href="https://agentmods.dev/skills/drvoss/everything-copilot-cli/triage"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/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.00045 | $0.01448 |
| Opus 5 | $0.00023 | $0.00724 |
| Sonnet 5 | $0.00009 | $0.00290 |
| Haiku 4.5 | $0.00005 | $0.00145 |
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 yesterday.
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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage
Use this skill to move one issue or one external-contributor pull request through a small, explicit triage workflow without losing context between sessions.
When to Use
- A bug report or feature request needs its first serious evaluation
- An existing issue has new comments and should be re-triaged
- An external-contributor pull request should be screened before deep review or merge discussion
- You need to decide whether work is ready for an agent, a human, more info, or closure
- The next step should be a durable tracker comment, not an implementation diff
When NOT to Use
| Instead of triage | Use |
|---|---|
| You need to bulk-process an issue backlog | github-issue-triage |
| You need to batch-triage a PR queue or manage PR lifecycle actions | github-pr-workflow |
| The feature is already approved and needs a PRD | create-prd |
| A plan or spec needs decomposition into implementation tickets | to-issues |
Prerequisites
- Access to the issue tracker, labels, and comment history
- A repo-specific mapping from conceptual states to actual label names, if labels already exist
- Enough codebase access to inspect related docs and attempt reproduction for bugs
- For PR triage, access to the diff, CI status, linked issues, and contributor role or
authorAssociation
Triage State Model
Use one category and one state:
- Categories:
bug,enhancement - States:
needs-triage,needs-info,ready-for-agent,ready-for-human,wontfix
If the project uses different label names, map them first and keep the conceptual model in your notes.
Workflow
1. Gather the full tracker context
Read:
- the issue or PR title and body
- existing labels
- comments and dates
- linked issues, checks, and changed files when the request surface is a PR
- related docs, glossary, ADRs, or prior issues in the same area
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.
- yesterday First seen · 183 lines · 45 tokens per session scan A 7f03870bcdaa
triage is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 1,448 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
speckit-workflow
Manage and run Spec Kit automation workflows via specify workflow. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use…
omc-ado-sprint
Sprint planning and iteration management for Azure DevOps projects. WHEN: User wants to plan sprints, manage iterations, check team capacity, groom backlogs, or assign work to sprints. DO NOT USE FOR: Work item triage (use omc-ado-triage), PR reviews (use omc-ado-review), pipeline management, or non-ADO projects.
omc-ado-setup
Configure Azure DevOps integration for the current project. WHEN: User wants to set up ADO integration, connect a project to Azure DevOps, configure .omg/config.json for ADO, or troubleshoot ADO connection issues. DO NOT USE FOR: Work item triage (use omc-ado-triage), sprint planning (use omc-ado-sprint), PR review…
omc-ado-triage
Azure DevOps work item triage — surfaces untriaged items, active work, open PRs, pipeline failures, and security alerts. WHEN: User wants to check ADO board status, triage work items, see pipeline health, review open PRs, or get a project health overview. DO NOT USE FOR: Sprint planning (use omc-ado-sprint), PR code…
omc-gh-project
GitHub Projects (v2) board management — list items, update status, manage iterations, and add issues/PRs to projects. WHEN: User wants to manage project boards, move cards between statuses, check project progress, or assign items to iterations. DO NOT USE FOR: Issue triage (use omc-gh-triage), PR review (use…
omc-gh-setup
Configure GitHub integration for the current project. WHEN: User wants to set up GitHub integration, connect a project to GitHub, configure .omg/config.json for GitHub, or troubleshoot GitHub connection issues. DO NOT USE FOR: Issue triage (use omc-gh-triage), project board management (use omc-gh-project), PR review…