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/consolidatenpx skills add darkroomengineering/cc-settings --skill consolidategit 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/consolidate)<a href="https://agentmods.dev/skills/darkroomengineering/cc-settings/consolidate"><img src="https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/consolidate.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.00043 | $0.00919 |
| Opus 5 | $0.00022 | $0.00460 |
| Sonnet 5 | $0.00009 | $0.00184 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
consolidate scanned grade A with 2 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
echo "Auto-memory entries:" && find ~/.claude/projects/*/memory -name "*.md" -not -name "MEMORY.md" 2>/dev/null | wc -l Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Enumerates other installed skillslowAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
echo "Skills:" && ls -d ~/.claude/skills/*/SKILL.md 2>/dev/null | wc -l Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consolidate Rules, Skills, and Learnings
Standalone Codex mode
Audit ${CODEX_HOME:-$HOME/.codex}/AGENTS.md, native
${CODEX_HOME:-$HOME/.codex}/agents/, native
${CODEX_HOME:-$HOME/.codex}/rules/, and the managed skills in the real
cc-settings checkout named by
${CODEX_HOME:-$HOME/.codex}/.cc-settings-version repo_path. Validate that
path is a git checkout of darkroomengineering/cc-settings before treating it
as source. The installed plugin/cache and darkroom/source runtime copy may be
read to diagnose drift, but must never be edited as though either were the git
source.
Claude auto-memory and CLAUDE.md cleanup are unavailable in standalone
Codex. Skip those counts and phases rather than redirecting them into
~/.claude. Verify native agent/rule references and managed source skill
triggers, then ask before deleting anything.
The remaining path examples describe Claude Code.
Phase 1: Audit
Count everything
echo "Rules:" && ls ~/.claude/rules/*.md 2>/dev/null | wc -l
echo "Skills:" && ls -d ~/.claude/skills/*/SKILL.md 2>/dev/null | wc -l
echo "Auto-memory entries:" && find ~/.claude/projects/*/memory -name "*.md" -not -name "MEMORY.md" 2>/dev/null | wc -l
echo "CLAUDE.md lines:" && wc -l ~/.claude/CLAUDE.md 2>/dev/null
echo "AGENTS.md lines:" && wc -l ~/.claude/AGENTS.md 2>/dev/null
Check for contradictions
Read all rules and flag:
- Opposites ("always X" in one, "never X" in another)
- Significant overlap (two rules covering the same concern)
- References to outdated tools, patterns, or dependencies
- Vague rules that aren't actionable
Check skill triggers
Read all skill descriptions and flag:
- Overlapping trigger phrases between skills
- Skills that never get invoked (ask the user)
- Outdated instructions
Phase 2: Merge and Deduplicate
Rules
- Merge rules covering the same concern
- Remove rules that duplicate AGENTS.md guardrails
- Remove rules for problems that no longer occur
- Tighten vague rules into specific instructions
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 · 118 lines · 43 tokens per session scan A bd5504d09558
consolidate is a skill published in the GitHub repository darkroomengineering/cc-settings (43 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 919 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 2 findings (reads agent configuration directories, enumerates other installed skills). 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.
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.
taskgo
Maintains a private Git-backed personal project and task control repository using concise current Markdown, derived Git history, ADRs, and status synchronization. Use when tracking tasks, updating project status (STATUS.md), managing ADRs, synchronizing tracker state, delegating tasks to external agents, or generating…
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…