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/rhuss/cc-spex/initnpx skills add rhuss/cc-spex --skill initgit clone --depth 1 https://github.com/rhuss/cc-spexWhat 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.00044 | $0.01371 |
| Opus 5 | $0.00022 | $0.00685 |
| Sonnet 5 | $0.00009 | $0.00274 |
| Haiku 4.5 | $0.00004 | $0.00137 |
Grade A, and why
init 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 2d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You MUST complete ALL steps below. Do not stop after Step 1.
Step 1: Run init script
Run the command from <spex-init-command> in the <spex-context> system reminder. This is your first and only Bash call. Do not run anything else before it.
- If output contains
NEED_INSTALL: show output, STOP. - If output contains
ERROR: show error, STOP. - If the command was run with
--refreshor--updateand output containsRESTART_REQUIRED: SKIP Steps 2 and 3. Templates and extensions were refreshed but the existing configuration (enabled extensions, permissions) is preserved. Go directly to Step 4 and report that the refresh completed. Tell the user to restart Claude Code. - If output contains
READYorRESTART_REQUIRED: do not summarize yet, go to Step 2.
Step 2: Ask about extensions and permissions
You MUST ask all 3 questions below in a SINGLE AskUserQuestion call. Do NOT split, merge, reword, or reorder them. Pass them exactly as specified:
-
(
multiSelect: true, header: "Quality"): "Which quality & review extensions do you want to enable?"- "spex-gates": "Quality gates on speckit commands (review-spec, review-code, verification)"
- "spex-deep-review": "Multi-perspective code review with autonomous fix loop (5 agents)"
- "spex-teams": "Parallel implementation with spec guardian review via Agent Teams (experimental, requires: spex-gates)"
-
(
multiSelect: true, header: "Workflow"): "Which workflow extensions do you want to enable?"- "spex-worktrees": "Git worktree isolation after speckit-specify (creates worktree in .claude/worktrees/)"
- "spex-collab": "Phase-split collaboration with REVIEWERS.md for team PRs"
- "spex-detach": "Strip spec artifacts at PR time for contributing to repos that don't use SDD"
-
(
multiSelect: false, header: "Permissions"): "How should spex commands handle permission prompts?"- "Standard (Recommended)": "Auto-approve spex plugin scripts (spex-init.sh, specify CLI)"
- "YOLO": "Auto-approve everything, bypass all permission prompts for unattended workflows"
- "None": "Confirm every spex command before execution"
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.
- 2d ago First seen · 87 lines · 44 tokens per session scan A a5641ffd2682
init is a skill published in the GitHub repository rhuss/cc-spex (114 stars, last pushed 13d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,371 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…