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 katalalab/katala-os --skill github-project-triagegit clone --depth 1 https://github.com/katalalab/katala-osWrote 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/katalalab/katala-os/github-project-triage)<a href="https://agentmods.dev/skills/katalalab/katala-os/github-project-triage"><img src="https://agentmods.dev/badge/skills/katalalab/katala-os/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/katalalab/katala-os/github-project-triage"><img src="https://agentmods.dev/badge/skills/katalalab/katala-os/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.00051 | $0.00506 |
| Opus 5.5 | $0.00020 | $0.00202 |
| Sonnet 5.5 | $0.00010 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00051 |
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 2mo 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
github-project-triage — issue and PR backlog management
Performs a structured triage pass on a repo's open issues and PRs.
When to use
- "このリポの issue をトリアージして"
- "古い PR を整理して"
- "バックログに何が溜まってるか確認して"
- Sprint planning prep
Do not use for:
- Closing issues without operator confirmation
- Reassigning issues to specific people without explicit instruction
Triage sequence
# 1. Overview
gh issue list --repo <owner>/<repo> --state open --limit 100 --json number,title,labels,createdAt,updatedAt
# 2. Stale issues (no activity >30d)
gh issue list --repo <owner>/<repo> --state open \
--json number,title,updatedAt \
--jq '[.[] | select(.updatedAt < (now - 2592000 | strftime("%Y-%m-%dT%H:%M:%SZ")))]'
# 3. Open PRs
gh pr list --repo <owner>/<repo> --state open --json number,title,labels,isDraft,createdAt,reviewDecision
# 4. Blocked items (label: blocked or waiting)
gh issue list --repo <owner>/<repo> --label "blocked,waiting" --state open
Output format
## Triage Report: <repo>
Date: YYYY-MM-DD
### Action Required (operator confirms each)
- CLOSE: #<n> — <reason>
- LABEL: #<n> — add <label>
- PRIORITIZE: #<n> — <reason>
### Stale (no activity >30d)
- #<n>: <title> (last active: <date>)
### Blocked
- #<n>: <title> — waiting on: <description>
Hard-rule reminders
- Present triage recommendations — do not execute without operator confirmation.
- Never close issues or PRs without operator approval.
- Label changes are lower risk but still confirm before applying.
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.
- 2mo ago First seen · 62 lines · 51 tokens per session scan A da4f9ea65813
github-project-triage is a skill published in the GitHub repository katalalab/katala-os (2 stars, last pushed 9d ago), licensed MIT. It adds 51 tokens to every session and 506 once invoked, about $0.0002 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-08-31.
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.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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.