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/darkroomengineering/cc-settings/triagenpx skills add darkroomengineering/cc-settings --skill triagegit clone --depth 1 https://github.com/darkroomengineering/cc-settingsWrote 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/darkroomengineering/cc-settings/triage)<a href="https://agentmods.dev/skills/darkroomengineering/cc-settings/triage"><img src="https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/triage.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.00051 | $0.00536 |
| Opus 5 | $0.00026 | $0.00268 |
| Sonnet 5 | $0.00010 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00054 |
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 4d 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.
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
- Record the current state with
git branch --show-current,git status --short,git log -1 --oneline, andgit 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. - Farolero coverage check. Read
package.jsonand record whether the repository declaresfarolero. Do not execute repository binaries during read-only triage, includingnode_modules/.bin/farolero: executable project dependencies can mutate state or expose credentials. If coverage is absent, note thatbun add -D farolero && bunx farolero baseline writeis an adoption path for the repository owner to run later. Do not install anything on an external repo. - Fan out
exploreagents 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)
- Rank findings: Critical / Should-fix / Cosmetic. Each with
file:lineand a one-line fix sketch. Max 15 findings — this is a triage, not an audit; recommend/audit codebaseif depth is warranted. - End with a split: "safe to fix directly" vs "needs client conversation".
Output
- Ranked findings table (Critical / Should-fix / Cosmetic)
- Org-boundary status: internal (fixes allowed) or external (report-only)
- Recommended next skill:
/fix,/audit codebase, or nothing
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.
- 4d ago First seen · 36 lines · 51 tokens per session scan A 2958b4132b98
triage is a skill published in the GitHub repository darkroomengineering/cc-settings (42 stars, last pushed 6d ago), licensed MIT. It adds 51 tokens to every session and 536 once invoked, about $0.0003 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-30.
Other skills, from other repositories
merge-pr
Merge a pull request with status checks, squash merge, and branch cleanup. Handles worktree contexts.
checkpoint
Quick 2-minute status update on current phase, completed work, blockers, and health check.
po-translate
Orchestrate English→Japanese translation of po/ja.po — classify, delegate translation/review to subagents, iterate until clean.
gui-debug
Verify a rendering or window-chrome change in any macOS GUI app unattended — find its CGWindowID via JXA, capture that window alone (with per-pixel alpha) using screencapture -l, and read exact RGBA via NSBitmapImageRep. Use for blur/opacity/corner-radius/glyph/color rendering bugs where a screenshot or pixel value is…
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
vibe
Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…