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 darkroomengineering/cc-settings --skill dr-reviewgit 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/dr-review)<a href="https://agentmods.dev/skills/darkroomengineering/cc-settings/dr-review"><img src="https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/dr-review/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/darkroomengineering/cc-settings/dr-review"><img src="https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/dr-review.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.00051 | $0.03202 |
| Opus 5.5 | $0.00020 | $0.01281 |
| Sonnet 5.5 | $0.00010 | $0.00640 |
| Haiku 4.5 | $0.00005 | $0.00320 |
Grade A, and why
dr-review 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 9d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Standalone Codex host setup
Claude frontmatter does not enforce a fork or reviewer identity in standalone
Codex. Keep the main pass read-only or create a fresh reviewer with
spawn_agent. Deliver context to a running reviewer with send_message, trigger
another turn for an idle existing reviewer with followup_task, wait with
wait_agent, and stop its current turn with interrupt_agent only when
necessary. Never spawn codex-verifier and never run codex-run.ts from inside Codex.
Writers share the working tree unless the live host explicitly offers
isolation. Reviewers may overlap because they are read-only; serialize any
later implementer and test-writer work with non-overlapping ownership. Gather
the current state by explicitly running git branch --show-current, git diff --staged --stat, and git diff --stat. The !command lines below are Claude
interpolation only.
Claude current state
- Branch: !
git branch --show-current 2>/dev/null || echo "unknown" - Staged files: !
git diff --staged --stat 2>/dev/null || echo "nothing staged" - Unstaged files: !
git diff --stat 2>/dev/null || echo "nothing unstaged"
Get Changes
# Unstaged changes
git diff
# Staged changes
git diff --staged
# Specific file
git diff path/to/file
Large diffs: walk a reading diff, not a summary
Past ~200 changed lines, present the walkthrough as a reading diff (the real diff, abridged, never a prose-only summary), following the "Reading diffs" protocol in /review-batch.
Standalone Codex review
Follow the native lifecycle above, then adjudicate the fresh reviewer's findings against the diff. The fresh agent supplies the independent review; skip the Claude bridge branch below.
Cross-model review (when the Codex bridge is available)
This skill runs as the Claude reviewer agent, often Claude reviewing a diff Claude just wrote, the self-preferential-bias case. The one cross-model Codex review per PR, /ship, or direct push (see CLAUDE-FULL.md "Claude and Codex routing") covers that case. Run it here only when the user asks or no Codex review has run for this PR (the reviewer has Bash, so call the bridge directly):
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.
- 9d ago First seen · 225 lines · 51 tokens per session scan A b01a1240f053
dr-review is a skill published in the GitHub repository darkroomengineering/cc-settings (52 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 3,202 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-10-20.
Other skills, from other repositories
hunk-launch-video
Produces Hunk videos by driving the real TUI headlessly in a PTY, compositing captioned 1080p frames in Chromium, and encoding with ffmpeg. Use for feature demos, workflow explainers, announcements, launch videos, and full-release roundups.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
hunk-release
Prepares, publishes, verifies, and curates Hunk releases. Use for release metadata, benchmarks, tags, publishing, release videos, backports, or recovery.
resolve-drive-pr
Drive an open PR through Polly/OCR, validation, and maintainer handoff.
describe-pr
Only use when the user explicitly invokes this skill by name.
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.