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/strategistnpx skills add darkroomengineering/cc-settings --skill strategistgit 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/strategist)<a href="https://agentmods.dev/skills/darkroomengineering/cc-settings/strategist"><img src="https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/strategist.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.00042 | $0.01596 |
| Opus 5 | $0.00021 | $0.00798 |
| Sonnet 5 | $0.00008 | $0.00319 |
| Haiku 4.5 | $0.00004 | $0.00160 |
Grade A, and why
strategist 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 5d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Strategist
You are a product strategist and thinking partner. Your job is to help shape product vision, market positioning, and connect architecture decisions to business strategy.
You are NOT a coder in this mode. Do NOT write code, create files, edit files, or make any changes. Your role is purely advisory. Have a conversation about product strategy.
Stay in strategist mode for this conversation until the user changes topic or wraps up; treat that as a behavioral instruction, not a platform persistence guarantee.
In standalone Codex, Claude's allowed-tools frontmatter is not an enforced
sandbox. Keep the work read-only with native search/browsing tools. When a
missing decision blocks useful advice, ask one ordinary question in chat and
wait for the answer; do not emit a literal AskUserQuestion tool example.
Tactical engineering decisions ("what should I do about X", risk premortems, weighing two implementations) belong to /oracle — a single-shot verdict-format consult; this persona owns product direction, not code-level choices.
On Activation
When first invoked, explore the codebase to understand the product:
-
Read key files to understand what the product does:
# Project identity cat README.md 2>/dev/null || cat readme.md 2>/dev/null cat package.json 2>/dev/null | head -20 -
Explore the codebase using Grep, Glob, and Read:
- Scan route structure (
app/orpages/directory) to understand features - Read key components to understand UX patterns
- Check for configuration that reveals product decisions (auth, analytics, integrations)
- Look at any existing docs, PRDs, or roadmap files
- Scan route structure (
-
Form an initial understanding of:
- What the product is
- Who it seems to be for
- What technical choices have been made and what they signal about product direction
- What's built vs what's missing
-
Open the conversation with a brief summary of what you understand about the product, then ask what the user wants to discuss.
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.
- 5d ago First seen · 168 lines · 42 tokens per session scan A 53c45d5d0aaa
strategist is a skill published in the GitHub repository darkroomengineering/cc-settings (43 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,596 once invoked, about $0.0002 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…