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 triage-issuegit 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/triage-issue)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/triage-issue"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/triage-issue/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/triage-issue"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/triage-issue.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.00017 | $0.01026 |
| Opus 5 | $0.00009 | $0.00513 |
| Sonnet 5 | $0.00003 | $0.00205 |
| Haiku 4.5 | $0.00002 | $0.00103 |
Grade A, and why
triage-issue-skill 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 8d 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.
This is a copy
95% identical to triage-issue — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Issue Skill
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.
Trigger
User provides a GitHub issue URL or number, e.g.:
/triage-issue 1970/triage-issue https://github.com/adenhq/hive/issues/1970
Workflow
Step 1: Fetch Issue Details
gh issue view <number> --repo adenhq/hive --json title,body,state,labels,author
Extract:
- Title
- Body (the claim/bug report)
- Current state
- Labels
- Author
If issue is already closed, inform user and stop.
Step 2: Analyze the Claim
Read the issue body and identify:
- The core claim - What is the user asserting?
- Technical specifics - File paths, function names, code snippets mentioned
- Expected behavior - What do they think should happen?
- Severity claimed - Security issue? Bug? Feature request?
Step 3: Investigate the Codebase
For each technical claim:
- Find the referenced code using Grep/Glob/Read
- Understand the actual implementation
- Check if the claim accurately describes the behavior
- Look for related tests, documentation, or design decisions
Step 4: Evaluate Validity
Categorize the issue as one of:
| Category | Action |
|---|---|
| Valid Bug | Do NOT close. Inform user this is a real issue. |
| Valid Feature Request | Do NOT close. Suggest labeling appropriately. |
| Misunderstanding | Prepare technical explanation for why behavior is correct. |
| Fundamentally Flawed | Prepare critique explaining the technical impossibility or design rationale. |
| Duplicate | Find the original issue and prepare duplicate notice. |
| Incomplete | Prepare request for more information. |
Step 5: Draft Response
For issues to be closed, draft a response that:
- Acknowledges the concern - Don't be dismissive
- Explains the actual behavior - With code references
- Provides technical rationale - Why it works this way
- References industry standards - If applicable
- Offers alternatives - If there's a better approach for the user
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.
- 8d ago First seen · 151 lines · 17 tokens per session scan A f2a7969bdacd
triage-issue-skill is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 1,026 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to triage-issue, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
bug-hunter
Use this skill when scanning source code for bugs, anti-patterns, code smells, or quality issues in a WrongStack project. Trigger on the explicit vocabulary — "bug", "bug hunt", "scan for issues", "find problems", "anti-pattern", "code smell", "static analysis" — and on the task shape, which is how it usually arrives…
git-flow
Use this skill when proposing, reviewing, or troubleshooting git commits, branches, pull requests, or merge strategies in a WrongStack project session. Triggers: user mentions "commit", "branch", "PR", "merge", "rebase", "stash", "diff".
shipping-a-pr
Use when finished work needs to ship as a pull request, or when the ask is about a PR — creating one, bringing it up to date, adding screenshots, watching its checks, or addressing its review comments. Not for reviewing a PR you are not shipping.
fix-worktree-opsx-skills-not-created
Diagnose/fix worktrees missing the generated openspec- (opsx) skills after worktreeInit. Root cause: bare npx openspec can resolve a squatted registry stub instead of the real CLI.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.