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 alexmond/alexmskills --skill ticket-triagegit clone --depth 1 https://github.com/alexmond/alexmskillsWrote 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/alexmond/alexmskills/ticket-triage)<a href="https://agentmods.dev/skills/alexmond/alexmskills/ticket-triage"><img src="https://agentmods.dev/badge/skills/alexmond/alexmskills/ticket-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/alexmond/alexmskills/ticket-triage"><img src="https://agentmods.dev/badge/skills/alexmond/alexmskills/ticket-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.00168 | $0.04266 |
| Opus 5 | $0.00084 | $0.02133 |
| Sonnet 5 | $0.00034 | $0.00853 |
| Haiku 4.5 | $0.00017 | $0.00427 |
Grade A, and why
ticket-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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ticket-triage
The recurring instruction is some form of "review tickets, prioritise, start in
parallel." This skill is the scheduler for that loop: it ranks, dispatches
isolated agents at an honest width, merges, and re-triages on every completion.
It schedules across tickets; what runs within a ticket is whatever the
ticket needs — a single role-briefed agent for most, a dev-crew relay for
multi-phase deliveries (see Composition).
First run: the repo profile
Triage rules are portable; the facts they act on are not. On first run in a repo
(and on "re-profile"), write .claude/ticket-triage/profile.md by inspecting the
repo and asking the user only what can't be read:
- Where the backlog lives — the issue tracker, plus any doc-based roadmap or plan files that also hold pending work.
- The verification command(s) — the repo's real gate (test/lint/build), so briefs name it instead of inventing one.
- Protected instances — any running dev server/port that belongs to the user and must never be stopped, restarted, or measured against.
- Merge policy — squash vs merge, who merges (default: the conductor, never the agent), required checks.
- Standing constraints — decisions already made (ADRs, conventions) that briefs must state so they aren't re-litigated per ticket.
Read the profile at the start of every run. If .claude/ticket-triage/
doesn't exist, this is a first run.
Start with the facts, not the ticket titles
bash <plugin>/scripts/backlog-snapshot.sh # issues, PRs, worktrees, recent main CI
bash <plugin>/scripts/backlog-snapshot.sh --brief # just issues + PRs
Read-only; it starts nothing and stops nothing. If the repo defines
.claude/ticket-triage/snapshot-extra.sh, the script runs it too — that is
where repo-specific facts (running instances, roadmap markers) come from.
The backlog is usually more than one place, and the doc-based part drifts — in the direction that wastes the most time: items describing shipped work as pending, or prescribing a measurement that can't answer its own question. Verify a doc-sourced item against the code before ranking it. If it is stale, fixing the doc is itself a ticket-sized piece of work worth doing.
What ships with it
3 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.
- 2d ago Changed · -7 lines a0a0b87eacef
- 3d ago Changed · +42 lines 5267cbcb5113
- 5d ago First seen · 292 lines · 168 tokens per session scan A fb3f4df3d6c0
ticket-triage is a skill published in the GitHub repository alexmond/alexmskills (6 stars, last pushed 2d ago), licensed MIT. It adds 168 tokens to every session and 4,266 once invoked, about $0.0008 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-05.
Other skills, from other repositories
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
dependency-upgrade
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.