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 skills add KevinZai/commander --skill ccc-saasgit 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-saas)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-saas"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-saas/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-saas"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-saas.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.01443 |
| Opus 5.5 | $0.00017 | $0.00577 |
| Sonnet 5.5 | $0.00009 | $0.00289 |
| Haiku 4.5 | $0.00004 | $0.00144 |
Grade A, and why
ccc-saas 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-saas — SaaS work, routed
CC Commander · $ccc-saas · the right SaaS method for the job, from scaffold to revenue.
SaaS sub-skills (saas-router, saas-scaffolder, better-auth, database-designer, drizzle-neon, api-design, backend-patterns, fastify-api, nextjs-app-router, shadcn-ui, tailwind-v4, stripe-subscriptions, billing-automation, webhook-patterns, multi-tenant, feature-flags, saas-metrics-coach, signup-flow-cro, paywall-upgrade-cro, form-cro) ship with the Commander CLI toolkit. Invoke one with the Skill tool when it is listed in this session; otherwise apply the focus in references/routing.md. The user's selected model is preserved.
Codex: ask pickers as plain-text questions.
When to use / when not to
- Use for a multi-user product with accounts, billing or tenants: new SaaS, adding auth or Stripe, schema and API design, upgrade and signup conversion, SaaS metrics.
- Use
$ccc-buildfor a plain web app, API or CLI without SaaS concerns,$ccc-designfor visual direction,$ccc-marketingfor acquisition beyond the product funnel,$ccc-datafor warehouse and analytics pipelines.
What happens
1. Detect the stack
Run in one Bash call, silent on failure:
test -f package.json && grep -oE '"(next|fastify|express|drizzle-orm|@neondatabase/serverless|prisma|better-auth|next-auth|@clerk/nextjs|stripe|tailwindcss|posthog-js|launchdarkly-node-server-sdk)"' package.json | sort -u
ls drizzle.config.* components.json prisma/schema.prisma 2>/dev/null
Render one line:
🏗️ Stack:
<tools detected | none detected>
2. Route by intent, or ask
An argument or a clear intent routes straight to the sub-skill(s) in references/routing.md. new, or no codebase with a build request, goes to step 3. A request that spans several areas (zero to MVP, add billing, growth) follows the matching campaign in that file, one sub-skill per step, and confirms the sequence with the user before the first write.
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.
- 5d ago Changed · -1 lines · -19 tokens per session d9b601a24b5d
- 18d ago Changed · +16 lines · +27 tokens per session f6773fcf38a1
- 1mo ago First seen · 84 lines · 35 tokens per session scan A f0f810d61f3e
ccc-saas 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,443 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
mcp-server-dev
Create MCP servers — multi-tool services exposed via Model Context Protocol. Use this skill whenever users mention MCP servers, building servers, server scaffolding, tool registration, or want to package tools for distribution via uvx or npx. Also use when the conversation involves stdio transport, server lifecycle…
mcp-tool-dev
Create MCP tools — individual tool functions exposed via Model Context Protocol. Use this skill whenever users mention MCP tools, tool handlers, tool functions, tool definitions, or want to add capabilities to an MCP server. Also use when the conversation involves designing tool schemas, writing tool descriptions, or…
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
agent-go-expert
Specialist subagent: Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
dotnet
Guidelines for .NET backend development with C#, ASP.NET Core, and Entity Framework Core.
microservices
Guidelines for building production-grade microservices with FastAPI/Python and Go, covering serverless patterns, clean architecture, observability, and resilience.