Borrowing it
Nothing to install: this file belongs to adityash8/openai-ads-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/adityash8/openai-ads-mcp/main/.claude/skills/github-project-triage/SKILL.mdgit clone --depth 1 https://github.com/adityash8/openai-ads-mcpWrote 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/adityash8/openai-ads-mcp/github-project-triage)<a href="https://agentmods.dev/skills/adityash8/openai-ads-mcp/github-project-triage"><img src="https://agentmods.dev/badge/skills/adityash8/openai-ads-mcp/github-project-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/adityash8/openai-ads-mcp/github-project-triage"><img src="https://agentmods.dev/badge/skills/adityash8/openai-ads-mcp/github-project-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.00084 | $0.00962 |
| Opus 5 | $0.00042 | $0.00481 |
| Sonnet 5 | $0.00017 | $0.00192 |
| Haiku 4.5 | $0.00008 | $0.00096 |
Grade A, and why
github-project-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 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Project Triage
Turn an open queue into decisions. Triage produces item cards a maintainer can act on, then sorts them so the orchestrator knows what to do.
Scope
- If invoked inside a Git repo with a GitHub remote (or a Routine cloned a specific repo), triage only that repo.
- Only broaden to multiple repos / the whole
ITSEZMONEYorg when the prompt explicitly saysall,broad,org-wide, oreverything.
Discover the queue
Use the GitHub MCP connector (preferred) or gh:
- Open PRs (with CI status, requested reviewers, draft state, mergeability).
- Open issues (with labels, age, last activity).
- For each, the last few comments and the CI job summary.
There is no repobar dependency — query GitHub directly. Batch reads where the
connector allows it; don't fetch full logs until an item needs them.
Item card
For every open issue/PR, produce:
| Field | What to capture |
|---|---|
| URL / # | Direct link. |
| What | One line: what this issue/PR is. |
| Why it matters | Impact / who it affects. |
| Author trust | Per the auto-merge allowlist: adityash8 = trusted; everyone else — other org members, returning/first-time/external contributors, forks, and bots (Dependabot/Renovate) — = untrusted. State the factual signal, not a vibe. |
| Type | bug · feature · dependency · security · docs · chore |
| Fit | good / mixed / poor + one-line reason (does it match the product?). |
| Risk | low / medium / high + blast radius (what breaks if wrong). |
| Proof | CI state · local repro · test coverage · manual/E2E validation. |
| Blockers | Missing repro, failing CI, needs decision, needs creds, merge conflict. |
| Next action | The single concrete next step. |
Trust here is an explicit allowlist for auto-merge, not a vibe: only
adityash8 is trusted. Untrusted authorship doesn't mean a bad patch — it means
the item cannot auto-merge and routes to needs-owner (draft PR), even with
green CI. The sole exception is a bot dependency bump, which may auto-merge
if it meets every low-risk gate. Trust never substitutes for green CI and a sane
diff; cite factual signals (account, prior merged PRs) when noting it.
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 · 82 lines · 84 tokens per session scan A 60309844593f
github-project-triage is a skill published in the GitHub repository adityash8/openai-ads-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 84 tokens to every session and 962 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
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.
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
tech-debt
Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.