triage

triage is a skill for Claude Code from darkroomengineering/cc-settings. It costs 42 tokens per session (511 once invoked), scanned A, original, MIT.

A read-only first review of an unfamiliar code repository that produces a ranked report of obvious problems.

In plain words
What is it for?
Use it to inspect repository status, check for declared coverage tooling, and identify glaring issues before deeper development or review.
Why use it?
It helps you assess a client or outside repository without changing files or sending changes back to its source. It also records the checkout state and notes when remote freshness is unknown.

Skill for Claude Code

Written for Claude Code: context: fork in frontmatter.

Part of the darkroom plugin — 24 skills, 11 agents, 4 hooks shipped together

Good fit Use it to inspect repository status, check for declared coverage tooling, and identify glaring issues before deeper development or review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/darkroomengineering/cc-settings/triage
Install

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.

Any agent
npx skills add darkroomengineering/cc-settings --skill triage
Clone the repo
git clone --depth 1 https://github.com/darkroomengineering/cc-settings

Made for: Claude Code.

Or install darkroom, the plugin that ships this one along with the rest of its 24 skills, 11 agents, 4 hooks.

Wrote 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.

agentmods badge for triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/triage/github.svg)](https://agentmods.dev/skills/darkroomengineering/cc-settings/triage)
Your own site
<a href="https://agentmods.dev/skills/darkroomengineering/cc-settings/triage"><img src="https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/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.

agentmods 80×15 button for triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/darkroomengineering/cc-settings/triage"><img src="https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 511 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.00511
Opus 5.5 $0.00017 $0.00204
Sonnet 5.5 $0.00008 $0.00102
Haiku 4.5 $0.00004 $0.00051

Measured 14d ago against content hash 3e43f2329def, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 14d 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.

skills/triage/SKILL.md · 30 lines

What it actually says

Repo Triage

First-pass sweep of a repo you didn't build. Output is a report, not a diff.

Guardrail (non-negotiable)

If the repo's origin is outside the darkroomengineering org: read-only. Never commit, never push, never open a PR (incident 2026-07-07). Findings go in the report; the user decides what crosses the org boundary. Check first:

git remote get-url origin

Pipeline

  1. Record the current state with git branch --show-current, git status --short, git log -1 --oneline, and git remote get-url origin. Do not checkout, pull, fetch, reset, stash, or otherwise change an external repository. State that freshness against the remote is unknown unless the current checkout already contains evidence that proves it.
  2. Farolero coverage check. Read package.json and record whether the repository declares farolero. Do not execute repository binaries during read-only triage, including node_modules/.bin/farolero: executable project dependencies can mutate state or expose credentials. If coverage is absent, note that bun add -D farolero && bunx farolero baseline write is an adoption path for the repository owner to run later. Do not install anything on an external repo.
  3. Fan out explore agents in ONE message:
    • (a) structure + dependency freshness
    • (b) TypeScript/lint/config hygiene
    • (c) obvious perf and a11y issues on key pages
    • (d) security smells (exposed env, secrets in history, unpinned actions)
  4. Rank findings: Critical / Should-fix / Cosmetic. Each with file:line and a one-line fix sketch. Max 15 findings — this is a triage, not an audit; recommend /audit codebase if depth is warranted.
  5. End with a split: "safe to fix directly" vs "needs client conversation". State the org-boundary status (internal: fixes allowed; external: report-only) and the recommended next skill: /fix, /audit codebase, or nothing.
Changes

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.

  1. 14d ago Changed · -6 lines 3e43f2329def
  2. 1mo ago Changed · -9 tokens per session 213362bd1654
  3. 2mo ago First seen · 36 lines · 51 tokens per session scan A 2958b4132b98

Subscribe to this mod's changes

triage is a skill published in the GitHub repository darkroomengineering/cc-settings (52 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 511 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-30.