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 markoblogo/abvx-agent-skills --skill repo-issue-triagegit clone --depth 1 https://github.com/markoblogo/abvx-agent-skillsWrote 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/markoblogo/abvx-agent-skills/repo-issue-triage)<a href="https://agentmods.dev/skills/markoblogo/abvx-agent-skills/repo-issue-triage"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/repo-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/markoblogo/abvx-agent-skills/repo-issue-triage"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/repo-issue-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.00058 | $0.00404 |
| Opus 5 | $0.00029 | $0.00202 |
| Sonnet 5 | $0.00012 | $0.00081 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
repo-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 9d 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.
What it actually says
Repo Issue Triage
Keep issues and backlog items moving through a small, explicit state machine.
Roles
Category:
bugenhancement
State:
needs-triageneeds-infoready-for-agentready-for-humanwontfix
Security-sensitive reports should first pass through authorized-security-router when scope, authorization, exploitability, or allowed verification level is unclear.
Workflow
- Read the full issue or request, including prior notes.
- Inspect only the relevant code and docs.
- Recommend category and state with reasoning.
- For bugs, attempt a minimal reproduction before asking for more info.
- If the request is underspecified, use grilling to close the gaps.
- Apply the outcome in the tracker or in a local markdown backlog.
Good Triage Notes
Capture:
- what is already established;
- what is still unclear;
- why the item is or is not ready for an agent;
- what exact human judgment is still needed.
Rules
- Every item should end up with one category and one state.
- Do not ask for vague "more info"; ask for specific missing evidence.
- For
wontfix, record the reason clearly enough that the same request is not rediscovered next week. - Keep the system output-neutral: GitHub issue, Linear ticket, markdown backlog, or internal tracker.
Final Report
State the category, the state, the reasoning, and the next actor: reporter, human maintainer, or agent.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 59 lines · 58 tokens per session scan A 232a14ee4f82
repo-issue-triage is a skill published in the GitHub repository markoblogo/abvx-agent-skills (16 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 404 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
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
incident-management
Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.
problem-management
Manage ServiceNow problems — create from linked incidents, proactive pattern detection, RCA with 5-Whys, knownerror workarounds (KEDB), KEDB search by CI/category/keywords, and permanent-fix linkage to changes.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
sap-session
A guided evidence-review process for diagnosing SAP operations without direct access to the live system, with a person collecting evidence and the agent reviewing it.
defect
A command for registering a software defect, meaning behavior that does not work as intended, and creating a task to fix it. The defect and its fix task receive tracked IDs and are stored in the project's backlog and task folders.