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 OutThisLife/brooklyn-skills --skill triagegit clone --depth 1 https://github.com/OutThisLife/brooklyn-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/outthislife/brooklyn-skills/triage)<a href="https://agentmods.dev/skills/outthislife/brooklyn-skills/triage"><img src="https://agentmods.dev/badge/skills/outthislife/brooklyn-skills/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/outthislife/brooklyn-skills/triage"><img src="https://agentmods.dev/badge/skills/outthislife/brooklyn-skills/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.00013 | $0.03916 |
| Opus 5.5 | $0.00005 | $0.01566 |
| Sonnet 5.5 | $0.00003 | $0.00783 |
| Haiku 4.5 | $0.00001 | $0.00392 |
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 15d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage
Investigate issues against current upstream, prove the disposition, and own the fix. For a real bug, consolidate competing PRs into one maintainer-owned replacement per root-cause cluster, preserving useful work and contributor credit. Do not bounce implementation back to reporters or contributors.
This skill is agent- and repository-independent. Use the host agent's available shell, file, search, and delegation capabilities; no particular tool API or runtime is required. Read companion skills by name using the host's skill loader or their SKILL.md files. Use gh for GitHub, glab for GitLab, or the forge's authenticated API. Repository instructions determine test commands and platform-specific validation.
When to use
/triage <issue URLs, numbers, range, or query>; a pasted report/thread is valid intake. Naming the skill in ordinary prose works too.- Backlog sweeps, duplicate/resolution investigations, and issue-to-fix maintainer passes.
- PR-only review belongs to
pr-triage; an already-owned PR's CI/reviews belong topr-ready.
Authority and scope
- Bare
/triageis investigate + verdict first, likepr-triage. No forge writes, implementation, commits, or pushes until authorized. Behavioral probes in disposable worktrees are allowed. - “Fix”, “ship”, “execute”, or “go” authorizes the agreed implementation/publishing scope. Authorization for an entire triage-and-fix sweep carries through without asking per issue. A fix-only request does not authorize unrelated closures. “Audit”, “recommendations only”, and explicit restrictions override execution defaults.
- Establish repository, selected issues, authority, and reviewed base once. Infer the current repo when unambiguous; ask only for genuinely missing scope. An unspecified
/triagedoes not authorize sweeping every repo. - An authorized fix-and-ship run includes rebase auto-merge for eligible low-risk PRs, enabled when they open under the gate below; do not ask again per PR. Risky or uncertain changes require separate merge authorization. Explicit no-merge/review-only instructions override this default. UI changes still require visual approval before checks/commits/publishing under
ui-only. - No auto-closure for age, popularity, speculative product taste, or failed local setup. Apply the repository's contribution/closure policy. Security reports follow private disclosure policy, not public reproduction comments.
What ships with it
1 file 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.
- 15d ago Changed 52af93e378e4
- 19d ago Changed · +7 lines 0ea36c9d1622
- 25d ago Changed · +3 lines f72bfe36bed9
- 27d ago First seen · 117 lines · 13 tokens per session scan A a90facb02967
triage is a skill published in the GitHub repository OutThisLife/brooklyn-skills (199 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 3,916 once invoked, about $0.0001 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-09-24.
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.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.