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 drvoss/everything-copilot-cli --skill github-issue-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/github-issue-triage)<a href="https://agentmods.dev/skills/drvoss/everything-copilot-cli/github-issue-triage"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/github-issue-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/skills/drvoss/everything-copilot-cli/github-issue-triage"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/github-issue-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.02359 |
| Opus 5.5 | $0.00024 | $0.00944 |
| Sonnet 5.5 | $0.00012 | $0.00472 |
| Haiku 4.5 | $0.00006 | $0.00236 |
Grade A, and why
github-issue-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 today.
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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Triage & Management
Why This is Copilot-Exclusive
GitHub access is built into Copilot CLI with no extra setup: the built-in GitHub MCP server (full
tool set when gh is absent, or when restored with the flags in the note below) or gh, which
the model is expected to use when it is installed. When exposed, the MCP issue tools add sub-methods for comments,
labels, and sub-issues. Either way Copilot reasons over the results directly. What is exclusive is the built-in GitHub MCP server, which needs no token or extension setup; when gh is installed, the model mostly uses gh, which any agent with a shell can also run.
Note: When
ghis on PATH, Copilot CLI omits these issue tools (list_issues,search_issues,issue_read) and the model is expected to useghinstead, e.g.gh issue list --state open --label <label>,gh issue view <n> --comments,gh search issues "<query>". To call the MCP tools, start the session with--add-github-mcp-tool=<name>for every GitHub MCP tool you need (it replaces the default set, so include default ones you still use), or--enable-all-github-mcp-tools, which also enables write tools.
When to Use
- Triaging a backlog of open issues across one or more repositories
- Auto-categorizing issues by content (bug, feature, docs, etc.)
- Finding duplicate or related issues before filing new ones
- Building one queue from both issues and external-contributor PRs
- Linking issues to pull requests for traceability
- Generating weekly issue reports or burndown summaries
Workflow
1. List Open Issues with Filters
With gh on PATH (default), e.g. gh issue list --repo my-org/my-app --state open --label bug --limit 25. When the MCP tools are exposed:
Tool: github-mcp-server-list_issues
owner: "my-org"
repo: "my-app"
state: "OPEN"
labels: ["bug"]
orderBy: "UPDATED_AT"
direction: "DESC"
perPage: 25
2. Search Across Repositories
Find issues matching a keyword across your entire org.
With gh on PATH (default), e.g. gh search issues "memory leak" --owner my-org --state open. When the MCP tools are exposed:
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.
- today Changed · +1 lines cf01cb451826
- yesterday Changed · +14 lines · +15 tokens per session a6f4b9f4d36a
- 2d ago Changed · +29 lines 6293775ab326
- 1mo ago First seen · 180 lines · 45 tokens per session scan A 724786f08089
github-issue-triage is a skill published in the GitHub repository drvoss/everything-copilot-cli (49 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 2,359 once invoked, about $0.0002 per session on Opus 5.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 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…
session-statusline
Manage only the current session's active statusline pills and clear entries without deleting work or changing enabled components. USE FOR: name this session, custom statusline name, label this terminal session, rename session label, clear session name, clear statusline, clear footer pills, remove a PR pill, remove an…
ask-navigator
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding, not building: it…
omc-ado-sprint
Azure DevOps sprint planning: manage iterations, check team capacity, groom the backlog, and assign work to sprints. Not for work item triage (omc-ado-triage), PR review, pipeline management, or GitHub repos (omc-gh-project).
omc-ado-setup
Set up or troubleshoot the Azure DevOps integration for this project (.omg/config.json connection). Not for triage, sprint planning, PR review, Azure cloud service config, or GitHub repos (omc-gh-setup).
omc-ado-triage
Triage Azure DevOps: board status, untriaged work items, active work, open PRs, pipeline failures, and security alerts for a project health overview. Not for sprint planning, PR code review, or GitHub repos (omc-gh-triage).