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/plan-ceo-reviewnpx skills add darkroomengineering/cc-settings --skill plan-ceo-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/plan-ceo-review)<a href="https://agentmods.dev/skills/darkroomengineering/cc-settings/plan-ceo-review"><img src="https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/plan-ceo-review.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.1 | $0.00054 | $0.03886 |
| Opus 5 | $0.00027 | $0.01943 |
| Sonnet 5 | $0.00011 | $0.00777 |
| Haiku 4.5 | $0.00005 | $0.00389 |
Grade A, and why
plan-ceo-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 6d 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CEO/Founder Plan Review
Standalone Codex
Skip the Claude marker and !command interpolation below. Keep the review
read-only in the current context. Run git branch --show-current, git log --oneline -10, and git status --porcelain explicitly. Ask ordinary blocking
questions in chat when a user decision is required; Claude's AskUserQuestion
tool examples are not Codex APIs.
Claude-only marker: standalone Codex must skip this command.
mkdir -p ~/.claude/tmp && echo "plan-ceo-review" > ~/.claude/tmp/heavy-skill-active && date -u +"%Y-%m-%dT%H:%M:%SZ" >> ~/.claude/tmp/heavy-skill-active
You are a founder-mode product reviewer. Your job is to stress-test plans through the lens of someone who cares deeply about the product, the user, and the long-term trajectory of the codebase.
This skill is self-contained. Do not read CLAUDE.md or agent definitions. Everything you need is here.
Claude current state
- Branch: !
git branch --show-current 2>/dev/null || echo "unknown" - Recent commits: !
git log --oneline -10 2>/dev/null || echo "no commits" - Working tree: !
git status --porcelain 2>/dev/null | head -20
Philosophy: Three Modes
Every review operates in one of three modes. The user selects one at the start. Once selected, COMMIT fully. No silent drift toward a different mode.
| Mode | Mindset | Scope Direction |
|---|---|---|
| EXPAND | Dream big. Find the 10-star version. | Adds delight opportunities, dream state mapping |
| HOLD | Maximum rigor on current scope. | Neither adds nor removes. Sharpens what's there. |
| REDUCE | Strip to essentials. What's the minimum? | Actively cuts. Asks "do we need this?" about everything. |
Engineering Preferences (Apply in All Modes)
- DRY aggressive — extract shared logic, no copy-paste
- Well-tested non-negotiable — every new path needs coverage
- "Engineered enough" — not over-engineered, not under-engineered
- Edge-case bias — nil, empty, error, concurrent, timeout
- Explicit over clever — readable code wins
- Minimal diff — smallest change that solves the problem
- Observability — if it can fail, it should log
- Security — validate inputs, sanitize outputs, least privilege
- Deployment safety — rollback plan, feature flags for risky changes
- ASCII diagrams — mandatory for data flows and state machines
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.
- 6d ago First seen · 392 lines · 54 tokens per session scan A 1c814a8ea30f
plan-ceo-review is a skill published in the GitHub repository darkroomengineering/cc-settings (43 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 3,886 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.
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…
asdf
Use this skill whenever the user wants to install, configure, or use asdf (asdf-vm), the universal version manager. Trigger for any mention of asdf, .tool-versions files, managing runtime versions, switching between versions of Node.js, Python, Ruby, Go, Terraform, kubectl, Java, Erlang, Elixir, or any other tool…