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/kevinzai/commander/ccc-contentnpx skills add KevinZai/commander --skill ccc-contentgit clone --depth 1 https://github.com/KevinZai/commanderWrote 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/kevinzai/commander/ccc-content)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-content"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-content.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.01173 |
| Opus 5 | $0.00022 | $0.00587 |
| Sonnet 5 | $0.00009 | $0.00235 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
ccc-content 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 3d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-content — Content creation
Placeholders like ~~social media and ~~email refer to connected tools. See CONNECTORS.md.
Create any type of content — from a single tweet to a full email sequence. Quick Mode produces a draft in under 3 questions. Power Mode runs the full pipeline: draft → review → schedule.
Quick Mode (default)
Ask three questions — use AskUserQuestion for Questions 1 and 3 (chip pickers). Question 2 is free-text (topic is inherently open-ended).
Question 1 — Content type:
Use AskUserQuestion with these chips (max 4; "Something else" covers remaining types):
question: "What kind of content are we creating?"
options:
- label: "📝 Blog post or article"
description: "Long-form — tutorial, opinion, how-to, case study."
- label: "📱 Social media posts"
description: "Twitter/X thread, LinkedIn post, Instagram caption."
- label: "📧 Email campaign or newsletter"
description: "Drip sequence, announcement, nurture, transactional."
- label: "💼 Something else"
description: "Marketing copy, landing page, docs, ads — describe in chat."
If user picks "Something else", ask one follow-up in chat: "Describe what you need — I'll produce it."
Question 2 — Topic (free-text — open-ended by nature): Ask in chat: "What's this about? One sentence is enough."
Question 3 — Audience:
Use AskUserQuestion with these chips:
question: "Who is this for?"
options:
- label: "👩💻 Developers"
description: "Engineers, technical founders, devtools users."
- label: "🚀 Founders / executives"
description: "Decision-makers, C-suite, startup founders."
- label: "🛒 Consumers"
description: "End users, general public, non-technical audience."
- label: "🏢 Internal team"
description: "Colleagues, employees, internal stakeholders."
Draft the content immediately. For social posts, generate platform-specific variations.
Power Mode
Activate by passing --power or detailed.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 147 lines · 43 tokens per session scan A eea9229f78f1
ccc-content is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,173 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-31.
Other skills, from other repositories
agent-workflow-designer
../../../engineering/skills/agent-workflow-designer/SKILL.md.
andreessen
../../../productivity/andreessen/skills/andreessen/SKILL.md.
moai-workflow-ddd
Domain-Driven Development workflow specialist using ANALYZE-PRESERVE-IMPROVE cycle for behavior-preserving code transformation. Use when refactoring legacy code or reducing technical debt safely.
hns-workflow-ci-loop
Unified CI watch + auto-fix loop skill. Polls gh pr checks after /moai sync PR creation, classifies required vs auxiliary failures, attempts safe automated patches (max 3 iterations), and escalates semantic failures to the user. Use for CI loop workflow — NOT for general loop iteration patterns (see…
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
fork-pr-operations
Operational patterns for fork PRs (head repo differs from base repo). Covers GitHub workflow approval after push, force-push protocol, remote naming conventions, stale CI verification, and bot review multi-round awareness. Load when working with fork PRs, cross-repo contributions, or workflow approval issues.