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/explorenpx skills add darkroomengineering/cc-settings --skill exploregit clone --depth 1 https://github.com/darkroomengineering/cc-settingsWhat 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.00064 | $0.00896 |
| Opus 5 | $0.00032 | $0.00448 |
| Sonnet 5 | $0.00013 | $0.00179 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
explore 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 yesterday.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Exploration
Delegates to the Explore agent for fast, read-only investigation of the codebase.
Standalone Codex
Claude frontmatter does not enforce a fork or tool restriction in standalone
Codex. Keep this workflow read-only yourself, or use spawn_agent with an
explore agent and a read-only prompt. Gather current state by explicitly
running pwd, basename "$PWD", ls package.json Cargo.toml go.mod pyproject.toml, and git rev-parse --show-toplevel; the !command lines below
are Claude interpolation only.
Codex does not receive TLDR from this package. In broad mode use rg --files,
rg -n exact searches, direct import searches, and focused file reads. In
upward-zoom mode search the symbol definition and all call sites with rg -n,
then trace imports and callers one layer up. Never claim a TLDR MCP ran.
Claude current state
- Directory: !
pwd 2>/dev/null - Project: !
basename "$(pwd)" 2>/dev/null - Stack: !
ls package.json Cargo.toml go.mod pyproject.toml 2>/dev/null || echo "unknown" - Git root: !
git rev-parse --show-toplevel 2>/dev/null || echo "not a git repo"
Two modes — pick by what the user asked
Broad investigation mode (default)
Use when the user is asking "how does X work" / "where is X" / "what handles Y" — finding code without a known starting point.
- Start broad - In Claude use
tldr semanticorGlob; in standalone Codex use the native searches above - Narrow down - Read specific files to understand implementation
- Trace connections - In Claude use
tldr impact; in standalone Codex trace callers and imports withrg - Summarize findings - Return clear, actionable summary
Upward-zoom mode
Use when the user is staring at a known function or module and needs to know how it fits — triggers like "zoom out", "bigger picture", "where does this fit", onboarding unfamiliar code.
- Follow ../context-doc/DOMAIN-AWARENESS.md — read
CONTEXT.mdand any relevant ADRs first if they exist. - Identify the symbol or file the user is asking about.
- In Claude, use TLDR for the structural answer:
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.
- yesterday First seen · 87 lines · 64 tokens per session scan A be400fd709d1
explore is a skill published in the GitHub repository darkroomengineering/cc-settings (42 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 896 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
dotfiles-bootstrap
Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.
astro-dso-doc
Generates a complete, polished HTML documentation page, a processing checklist, an AstroBin post JSON, a PixInsight process icon set (XPSM), AND a ready-to-paste PixInsight project Description field for a deep-sky object (DSO) astrophotography project. Use this skill whenever the user mentions astrophotography, a DSO…
document-code
Apply Google Style documentation standards to Python, Go, TypeScript, and Terraform code. Use when writing or reviewing code that needs docstrings/comments/JSDoc, when asked to "document this code", "add docstrings", "follow Google Style", or when improving code documentation quality. Supports Python docstrings, Go…
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.
datadog
Use this skill when you need to search Datadog logs, query metrics, tail logs in real-time, trace distributed requests, investigate errors, compare time periods, find log patterns, check service health, or export observability data.
document-project
Generate comprehensive, professional project documentation structures including README, ARCHITECTURE, USERGUIDE, DEVELOPERGUIDE, and CONTRIBUTING files. Use when the user requests project documentation creation, asks to "document a project", needs standard documentation files, or wants to set up docs for a new…