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 agentmods add skills/everywan-dev/claude-code-engineering/triage-issues-and-prsnpx skills add everywan-dev/claude-code-engineering --skill triage-issues-and-prsgit clone --depth 1 https://github.com/everywan-dev/claude-code-engineeringWrote 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/everywan-dev/claude-code-engineering/triage-issues-and-prs)<a href="https://agentmods.dev/skills/everywan-dev/claude-code-engineering/triage-issues-and-prs"><img src="https://agentmods.dev/badge/skills/everywan-dev/claude-code-engineering/triage-issues-and-prs.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.01722 |
| Opus 5 | $0.00022 | $0.00861 |
| Sonnet 5 | $0.00009 | $0.00344 |
| Haiku 4.5 | $0.00004 | $0.00172 |
Grade A, and why
triage-issues-and-prs 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 3d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage
Move issues on the project issue tracker through a small state machine of triage-issues-and-prs roles.
If this repo treats external pull requests as a request surface (see the issue-tracker config), triage-issues-and-prs covers them too: a PR is an issue with attached code, using the same roles, same states, and same machine, with a few deltas marked "for a PR" below. Resolve a bare #42 to an issue or PR per the tracker config.
Every comment or issue posted to the issue tracker during triage-issues-and-prs must start with this disclaimer:
> *This was generated by AI during triage-issues-and-prs.*
Reference docs
- AGENT-BRIEF.md: how to write durable agent briefs
- OUT-OF-SCOPE.md: how the
.out-of-scope/knowledge base works
Roles
Two category roles:
bug: something is brokenenhancement: new feature or improvement
Five state roles:
needs-triage: maintainer needs to evaluateneeds-info: waiting on reporter for more informationready-for-agent: fully specified, ready for an AFK agentready-for-human: needs human implementationwontfix: will not be actioned
For a PR, the same states read against the attached code: ready-for-agent means a brief is attached and an agent should take the next step on the diff; ready-for-human means it's ready for a human to merge.
Every triaged issue should carry exactly one category role and one state role. If state roles conflict, flag it and ask the maintainer before doing anything else.
These are canonical role names. The actual label strings used in the issue tracker may differ. The mapping should have been provided to you. If not, tell the user to run /set-up-the-issue-tracker.
State transitions: an unlabeled issue normally goes to needs-triage first; from there it moves to needs-info, ready-for-agent, ready-for-human, or wontfix. needs-info returns to needs-triage once the reporter replies. The maintainer can override at any time; flag transitions that look unusual and ask before proceeding.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 117 lines · 43 tokens per session scan A 2751539f1e1f
triage-issues-and-prs is a skill published in the GitHub repository everywan-dev/claude-code-engineering (2 stars, last pushed 14d ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,722 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
claude-project-manifest
Creates annotated bibliography-style manifests for Claude projects, tracking files, conversation threads, and relationships with unique IDs and annotations. Use when documenting project contents, creating file inventories, tracking conversation history, or building navigable knowledge maps.
proofpress
Preserve or inspect decision history for Markdown and static HTML knowledge artifacts with Proofpress. Use when creating or accepting a meaningful revision to an ADR, design doc, PRD, README, strategy note, portable .md artifact, or static .html/.htm artifact in a configured repository, or when receiving a file…
llm-wiki
Maintain a personal team knowledge base using the LLM Wiki pattern — incremental ingest, query, and lint operations on a layered wiki architecture.
PBE Extractor
Extract invariant principles from any text — find the ideas that survive rephrasing.
Principle Synthesizer
Synthesize invariant principles from 3+ sources — find the core that survives across all expressions.
book-to-skill
Use when convert technical books and documents (PDF, EPUB, DOCX, HTML, Markdown, RTF, MOBI) into structured agent skills with frameworks, mental models, chapter references, and decision rules. Includes full extraction pipeline. Use when the user wants to turn a book or document collection into a reusable agent skill…