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 pmatos/skills --skill pm-triagegit clone --depth 1 https://github.com/pmatos/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/pmatos/skills/pm-triage)<a href="https://agentmods.dev/skills/pmatos/skills/pm-triage"><img src="https://agentmods.dev/badge/skills/pmatos/skills/pm-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/pmatos/skills/pm-triage"><img src="https://agentmods.dev/badge/skills/pmatos/skills/pm-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.00121 | $0.03692 |
| Opus 5.5 | $0.00048 | $0.01477 |
| Sonnet 5.5 | $0.00024 | $0.00738 |
| Haiku 4.5 | $0.00012 | $0.00369 |
Grade A, and why
pm-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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pm-triage — Decision Session for Blocked Issues
Some issues aren't blocked on code — they're blocked on a decision only a human with technical vision and product context can make. This skill runs a per-project decision session over exactly those issues: it gathers every open issue flagged needs-triage, human-needed, or sym:human-needed (the label symphonika inserts on personal projects), works out which of them are stale or already resolved, and walks the rest past the user one at a time so each decision unblocks implementation immediately.
Scope is one project per run. Pass owner/repo to target a repository other than the current one; with no argument, infer the repo from the current git remote.
Why no local state file
Every decision is written back to GitHub itself — a comment recording the decision and a label removal — so the label is the queue. The next /pm-triage run re-queries open issues carrying the target labels and naturally picks up wherever the last session left off, including a session that ended early. Nothing needs to be tracked locally, and nothing can drift out of sync with what actually happened on the issue.
Arguments
owner/repo— triage this repository instead of the current one.--labels a,b,c— use exactly this label set instead of the defaultneeds-triage,human-needed,sym:human-needed. Replaces the default entirely; include all the labels you want considered.
Workflow
1. Resolve the repo and the label set
Determine the repo: the owner/repo argument if given, otherwise gh repo view --json nameWithOwner -q .nameWithOwner. Bail with a clear message if neither works (not a git repo, no gh auth, or gh unavailable — this skill is gh-only; it never uses a GitHub MCP server, since it targets arbitrary owner/repo values that may not be the current project).
Determine the label set: --labels if given, otherwise the three defaults. Check which of them actually exist in the repo with gh label list --repo <repo> --json name --limit 1000 -q '.[].name' — --limit defaults to 30, and a repo with more labels than that would otherwise make a real target label look absent. Keep only the labels that exist.
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 First seen · 156 lines · 121 tokens per session scan A f1a1e7a0d2a4
pm-triage is a skill published in the GitHub repository pmatos/skills (2 stars, last pushed 2d ago), licensed MIT. It adds 121 tokens to every session and 3,692 once invoked, about $0.0005 per session on Opus 5.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-04.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.