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 mattmre/EVOKORE-MCP-PUBLIC --skill github-triagegit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/mattmre/evokore-mcp-public/github-triage)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/github-triage"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/github-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/mattmre/evokore-mcp-public/github-triage"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/github-triage.svg" alt="Reviewed on agentmods" width="80" 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.00062 | $0.02582 |
| Opus 5 | $0.00031 | $0.01291 |
| Sonnet 5 | $0.00012 | $0.00516 |
| Haiku 4.5 | $0.00006 | $0.00258 |
Grade A, and why
github-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 5d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
github-triage — Label-Based Issue State Machine
When to use this skill
Use when there is at least one open GitHub issue in this repository that
needs to be moved through the triage state machine (see ADR-0006). The
skill replaces the upstream "maintainer manually triggers" model with an
agent-driven transition: the agent reads the issue body, the labels,
linked artifacts under docs/, and the latest evidence/replay JSONL,
then decides the next state.
If there are no open issues, stop. If the only open issues are already
in terminal states (triage:done, triage:wontfix), stop. If a
docs/agent-briefs/<issue-number>.md artifact already exists for the
issue but the issue's labels do not match the brief's recommended next
state, fix the brief first.
Adapted From Upstream
This skill is adapted from mattpocock/skills/github-triage (upstream
commit 90ea8eec03d4ae8f43427aaf6fe4722653561a42, MIT-licensed). The
upstream skill uses 7 labels with a documented transition table, an
AGENT-BRIEF.md artifact pattern, and an .out-of-scope/ knowledge
base. EVOKORE-MCP keeps all three but rewires the transition triggers
from "maintainer comments on the issue" to "agent reads evidence and
applies the rule".
EVOKORE-Specific Adaptations
| Upstream behavior | EVOKORE behavior |
|---|---|
| "Maintainer triggers triage" | Agent runs this skill against gh issue list --state open --json number,labels,title and transitions automatically per the rule below |
| "User describes the bug to triage" | Read the issue body + linked docs/bugs/<slug>.md (if present) + most recent evidence JSONL; route ambiguity to triage:human-review |
| "Human writes the agent brief" | Agent writes docs/agent-briefs/<issue-number>.md from the issue body + linked artifacts |
| "Human applies labels" | Agent emits the label transition; actual gh issue edit --add-label calls are gated by EVOKORE_AUTO_LABEL_ISSUES=true (DC-43) |
| "Maintainer dismisses out-of-scope items" | Agent writes .out-of-scope/<slug>.md with rationale and emits the triage:wontfix label transition |
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.
- 5d ago First seen · 226 lines · 62 tokens per session scan A 4537b53c9571
github-triage is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 2,582 once invoked, about $0.0003 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
github-project-management
GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
mk:ghpm
GitHub project management via the gh CLI — create and triage issues, manage GitHub Projects v2 boards (add items, update status fields), manage labels and milestones, and generate handoff-status summaries. Use when "create a GitHub issue", "add to project board", "update sprint status", "create label/milestone", or…
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
triage
Use this skill to systematically triage, categorize, prioritize, and label incoming issues, bug reports, and feature requests. Verifies reproducibility, identifies affected components, and assigns standardized workflow labels.