Borrowing it
Nothing to install: this file belongs to the-sid-dani/second-brain-os. 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/the-sid-dani/second-brain-os/main/.agents/skills/triage/SKILL.mdgit clone --depth 1 https://github.com/the-sid-dani/second-brain-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/the-sid-dani/second-brain-os/triage)<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/triage"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/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/the-sid-dani/second-brain-os/triage"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/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.00133 | $0.02189 |
| Opus 5.5 | $0.00053 | $0.00876 |
| Sonnet 5.5 | $0.00027 | $0.00438 |
| Haiku 4.5 | $0.00013 | $0.00219 |
Grade A, and why
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 7d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage
Move tickets on the project's tracker through a small state machine of triage roles. The work can be code or knowledge work.
Resolve the project and its paths from docs/agents/project-context.md. If a skill earlier in this conversation already resolved them, reuse that.
Every comment posted during triage must start with this disclaimer:
> *This was generated by AI during triage.*
Reference docs
- AGENT-BRIEF.md — how to write durable agent briefs
- OUT-OF-SCOPE.md — how rejected requests are recorded and matched later
Roles
The category is the ticket's type:
Bug— something is brokenStory— a new capability or deliverableTask— prep, setup, cleanup, an approval step, anything that isn't new capability
Five state roles:
needs-triage— maintainer needs to evaluateneeds-info— waiting on the requester for more informationready-for-agent— fully specified, ready for an AFK agentready-for-human— fully specified, but a person has to do itwontfix— will not be actioned
Every triaged ticket should carry exactly one category and one state: the **Type:** and **Status:** lines of the ticket file. If the state looks contradictory (for example a Won't fix ticket with open work under it), flag it and ask the maintainer before doing anything else.
State transitions: an untriaged ticket 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 requester replies. The maintainer can override at any time — flag transitions that look unusual and ask before proceeding.
Invocation
The maintainer invokes /triage and describes what they want in natural language. Interpret the request and act. Examples:
- "Show me anything that needs my attention"
- "Let's look at ticket 04"
- "Move ticket 04 to ready-for-agent"
- "What's ready for agents to pick up?"
- "Triage ticket 04 in the second-brain project"
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.
- 7d ago First seen · 133 lines · 133 tokens per session scan A c388c8766f40
triage is a skill published in the GitHub repository the-sid-dani/second-brain-os (3 stars, last pushed 7d ago), licensed MIT. It adds 133 tokens to every session and 2,189 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-10-17.
Other skills, from other repositories
peer-onboard
A procedure for bringing an outside lead or peer into a shared working setup, including their contact space, records, previous conversations, and ongoing session.
contrib-watch
Watch incoming feedback from outside engineers on your open-source repos: comments, reviews, issues, mentions. Use when you need to find who replied to your pull requests or issues, triage human versus bot responses, and answer within a day with evidence.
retro-lost
Run a retrospective for an abandoned agent session (untouched for over 24 hours, never closed with a retro): rebuild context cold from the transcript, list what was built, sort Keep/Drop/Try and file the durable parts. Use from a nightly routine or on demand. Triggers: /retro-lost, retro for an abandoned session.
issue-match
Measure a target repository's queue and find a live open issue the contribution would close, before opening a pull request there. Reports how many PRs are open, how many of the last N closed ones were actually merged, and which issue to attach to, because a cold PR into a dead queue is a wasted artifact. Triggers…
local-engineer-outreach
An engineer-outreach workflow that manages ongoing conversations with engineering contacts and moves them through planned next steps toward an invitation or call to action.
outbound-gate
Gate for any outbound message before it leaves: pull request or issue comment, DM, invite, post, email. Use before sending to check facts, tone, platform rules, registry status and AI-slop, and to block text that fails.