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 rhuss/cc-spex --skill initgit clone --depth 1 https://github.com/rhuss/cc-spexWrote 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/rhuss/cc-spex/init)<a href="https://agentmods.dev/skills/rhuss/cc-spex/init"><img src="https://agentmods.dev/badge/skills/rhuss/cc-spex/init/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/rhuss/cc-spex/init"><img src="https://agentmods.dev/badge/skills/rhuss/cc-spex/init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 32 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 33 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00044 | $0.01522 |
| Opus 5.5 | $0.00018 | $0.00609 |
| Sonnet 5.5 | $0.00009 | $0.00304 |
| Haiku 4.5 | $0.00004 | $0.00152 |
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 yesterday.
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 — 88 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
ERRORor the script exits with a non-zero status other than3(3meansRESTART_REQUIRED): show the error, STOP. Do not continue to Step 2, Step 3 or the restart advice.- In particular, init exits with status
1andERROR: spex-worktrees requires the spec-kit git extensionwhenspex-worktreesis enabled but thegitextension cannot be enabled. Show the message with its two fixes (specify extension add git/specify extension enable git, orspecify extension disable spex-worktrees) and tell the user to run/spex:initagain afterwards.
- In particular, init exits with status
- 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: speckit-specify creates the worktree (in .claude/worktrees/) before the feature branch, so the main checkout never switches (requires the git extension)"
- "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"
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.
- yesterday Changed · +1 lines f9be3e26c75c
- 1mo ago First seen · 87 lines · 44 tokens per session scan A a5641ffd2682
init is a skill published in the GitHub repository rhuss/cc-spex (120 stars, last pushed 2d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,522 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.