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.
git 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/plugins/alexmond/alexmskills/ticket-triage)<a href="https://agentmods.dev/plugins/alexmond/alexmskills/ticket-triage"><img src="https://agentmods.dev/badge/plugins/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/plugins/alexmond/alexmskills/ticket-triage"><img src="https://agentmods.dev/badge/plugins/alexmond/alexmskills/ticket-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 1mo 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
{
"name": "ticket-triage",
"description": "Backlog-drain loop: rank the open tickets, dispatch the genuinely startable ones in parallel (worktree-isolated, role-briefed, honest width), verify and merge each result, and re-triage on every completion until the queue is empty or everything left needs the user.",
"version": "0.4.2",
"author": {
"name": "Alex Mondshain",
"email": "[email protected]"
},
"homepage": "https://www.alexmond.org/alexmskills/ticket-triage/",
"repository": "https://github.com/alexmond/alexmskills",
"license": "MIT",
"keywords": [
"triage",
"backlog",
"tickets",
"parallel",
"worktree",
"orchestration"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 126 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago Changed 9a3145eae588
- 1mo ago Changed b445b0cdd9c6
- 1mo ago Changed · +7 lines fe840e2c78b0
- 1mo ago First seen · 14 lines scan A 8a06ac14199d
ticket-triage is a plugin published in the GitHub repository alexmond/alexmskills (9 stars, last pushed 9d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.
github-activity
Read-only GitHub activity reporter for program managers. One hosted connector reads merged pull requests, opened and closed issues, and milestone movement across several repositories since a point in time. It holds no write tool, the tool policy allows only the read tool so anything else fails closed, and the…
trailhead
Start and drive large projects as a map of tickets on GitHub Issues, resolving one at a time. Map-based onboarding + a discuss→plan→execute→verify engine with atomic commits, all on the Issues. Ships as a dispatcher plus cohesion-clustered skills over a shared core; depends on nothing beyond an authenticated gh CLI.
agent-dispatch
Start issue-to-pr runs from GitHub labels on your own machine: a scheduled tick picks the issue you labelled agent, or the one you replied on, and runs it headless under your own Claude Code or Codex login, on Windows, macOS or Linux.
gh-tools
GitHub workflow automation: GFM link validation, WebFetch enforcement, issue management, fork intelligence.
g-forge
Educated, enforced project management for AI development - a PM layer, parallel implementation waves, and a git-hook commit gate that can't be skipped. Make any model ship like a senior team.