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 commands/evan043/claude-cli-advanced-starter-pack/ccasp-setup.templategit clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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/commands/evan043/claude-cli-advanced-starter-pack/ccasp-setup.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/ccasp-setup.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/ccasp-setup.template.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.00000 | $0.04532 |
| Opus 5 | $0.00000 | $0.02266 |
| Sonnet 5 | $0.00000 | $0.00906 |
| Haiku 4.5 | $0.00000 | $0.00453 |
Grade A, and why
ccasp-setup.template 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 4d 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 — 542 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
ccasp-setup — Codex Runtime
CCASP Setup in Codex works differently — instead of writing to CLAUDE.md (which Claude Code reads), project config goes in AGENTS.md (which Codex reads).
What /ccasp-setup Does
Configures your project with:
- GitHub repository details
- Deployment targets (Railway/Cloudflare)
- Tech stack detection
- Testing configuration
Running Setup in Codex
Step 1: Tell me what you want to configure. I'll ask the minimum required questions:
- What is your GitHub repo? (owner/repo)
- What platform is your backend on? (Railway/Heroku/render/fly/vercel)
- What platform is your frontend on? (Cloudflare/Vercel/Netlify)
Step 2: I'll write the config to AGENTS.md under a project config section (Codex-readable) instead of CLAUDE.md.
Step 3: I'll also create/update .ccasp/config.yaml with runtime settings.
Note: For full CLAUDE.md-based project config (used by Claude Code CLI), run /ccasp-setup in Claude Code.
description: CCASP Setup Wizard - one-shot linear project configuration model: sonnet
CCASP Setup Wizard
Linear setup wizard that configures your entire project in one pass. No menus to revisit.
Instructions for Claude
This is a linear wizard - walk through each step sequentially, collecting all inputs before writing config at the end.
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.
- 4d ago First seen · 542 lines · 0 tokens per session scan A cbda1fad34db
ccasp-setup.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,532 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.