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/github-issue-triagenpx skills add drvoss/everything-copilot-cli --skill github-issue-triagegit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWhat 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.01476 |
| Opus 5 | $0.00023 | $0.00738 |
| Sonnet 5 | $0.00009 | $0.00295 |
| Haiku 4.5 | $0.00005 | $0.00148 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 180 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
Copilot CLI has native GitHub Issue tools baked into its MCP server — list_issues,
search_issues, issue_read with sub-methods for comments, labels, and sub-issues. These
structured tool calls return rich, typed data that Copilot can reason over directly. Claude Code
has no built-in GitHub integration and must rely on gh issue list with fragile text parsing.
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
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:
Tool: github-mcp-server-search_issues
query: "memory leak is:open"
owner: "my-org"
3. Read Issue Details and Comments
Tool: github-mcp-server-issue_read
method: "get"
owner: "my-org"
repo: "my-app"
issue_number: 87
Tool: github-mcp-server-issue_read
method: "get_comments"
owner: "my-org"
repo: "my-app"
issue_number: 87
4. Check Sub-Issues
For tracking epics and parent/child relationships:
Tool: github-mcp-server-issue_read
method: "get_sub_issues"
owner: "my-org"
repo: "my-app"
issue_number: 42
5. Get Labels for Classification
Tool: github-mcp-server-issue_read
method: "get_labels"
owner: "my-org"
repo: "my-app"
issue_number: 87
6. Pull External-Contributor PRs into the Queue
If the inbox includes PRs as well as issues, filter for outside contributors first and then route those PRs through the same triage state model you use for issues.
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 · 180 lines · 45 tokens per session scan A 724786f08089
github-issue-triage is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 6d ago), licensed MIT. It adds 45 tokens to every session and 1,476 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-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…
declare
Analyzes task plan and declares files that will be created or modified, producing declared-files.json.
execute
Executes the implementation plan for a Formic task.
launch-command
Launch orchestration and readiness assessment engine with cross-functional workstream tracking and go/no-go gates. Use when: launch readiness, launch checklist, launch orchestration, go no go, launch plan, are we ready to launch.
decompose
Decompose a feature spec into work items for orchestration via nw. Takes a PRD, phase doc, or verbal description and breaks it into human-reviewable PR-sized work items with dependencies mapped into batches. Use when asked to "decompose", "break down this feature", "create work items for", or "plan the work items".
friction-triage
Interactively walk through every friction log in .ninthwave/friction/ one at a time. For each log: read it, assess severity and possible duplicates, ask the human what to do (fix now / create work item / update doc / drop / merge / skip), execute the decision, and delete the log. This is the canonical way to clear the…