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 britt/agent-skills --skill triage-new-issuesgit clone --depth 1 https://github.com/britt/agent-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/britt/agent-skills/triage-new-issues)<a href="https://agentmods.dev/skills/britt/agent-skills/triage-new-issues"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/triage-new-issues/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/britt/agent-skills/triage-new-issues"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/triage-new-issues.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.00047 | $0.00828 |
| Opus 5 | $0.00023 | $0.00414 |
| Sonnet 5 | $0.00009 | $0.00166 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
triage-new-issues 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 9d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage New Issues Skill
Review new or untriaged GitHub issues, assess priority based on urgency signals, suggest labels, and recommend owners.
When to Use
Activate when:
- Processing new incoming issues
- Reviewing untriaged backlog
- Assessing issue priority
- Assigning issues to owners
Fetching and Applying Triage
Use the gh CLI (must be installed and authenticated):
# Find untriaged issues
gh issue list --search 'no:label' --json number,title,body,labels
# Apply labels after triage
gh issue edit <n> --add-label <label>
Priority Signals
Critical (P0)
Keywords: "down", "outage", "security", "vulnerability", "production", "urgent", "ASAP", "breach"
Labels: critical, security, production
Action: Immediate attention required
High (P1)
Keywords: "blocking", "regression", "broken", "can't use", "data loss", "crash"
Labels: blocker, regression, priority/high
Action: Address this sprint
Medium (P2)
Keywords: "bug", "incorrect", "should", "expected", "wrong"
Labels: bug, priority/medium
Action: Schedule for upcoming sprint
Low (P3)
Keywords: "nice to have", "minor", "cosmetic", "enhancement", "workaround exists"
Labels: enhancement, low-priority
Action: Add to backlog
Triage Guidelines
Assessment Process
- Read title and full description
- Scan for urgency keywords and labels
- Check for existing labels that signal priority
- Assess impact (how many users affected)
- Look for workarounds mentioned
- Check if duplicate of existing issue
- Determine ownership: check CODEOWNERS, recent
git logon affected paths, or past assignees of similar issues — omit the assignee suggestion if none found
When to Escalate
- Security vulnerabilities → Flag immediately
- Production outages → Notify on-call
- Data integrity issues → High priority regardless of other signals
When to Ask Questions
- Unclear reproduction steps
- Missing environment details
- Ambiguous severity ("it's broken" but unclear impact)
- No indication of urgency or timeline
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.
- 9d ago First seen · 118 lines · 47 tokens per session scan A 11a8f3d05494
triage-new-issues is a skill published in the GitHub repository britt/agent-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 47 tokens to every session and 828 once invoked, about $0.0002 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
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.