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.
git 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/plugins/rhuss/cc-spex/spex)<a href="https://agentmods.dev/plugins/rhuss/cc-spex/spex"><img src="https://agentmods.dev/badge/plugins/rhuss/cc-spex/spex/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/plugins/rhuss/cc-spex/spex"><img src="https://agentmods.dev/badge/plugins/rhuss/cc-spex/spex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
spex 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.
What it actually says
{
"name": "spex",
"version": "6.1.0",
"description": "Specification-Driven Development with Process Discipline for AI Agents",
"author": {
"name": "Roland Huss",
"email": "[email protected]"
},
"license": "MIT",
"repository": "https://github.com/rhuss/cc-spex",
"homepage": "https://github.com/rhuss/cc-spex",
"keywords": [
"claude-code",
"plugin",
"specification-driven-development",
"spex",
"specs",
"test-driven-development",
"tdd",
"process-discipline",
"quality-gates",
"extensions"
],
"hooks": "./hooks.json"
}
What it installs
The manifest is a name and a version. 1 skill, 8 commands travel with it, and installing the plugin installs all of them — 183 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill init A 44 tokens
- Command speckit.spex-collab.phase-manager A 15 tokens
- Command speckit.spex.walkthrough A 27 tokens
- Command speckit.spex-collab.reviewers A 12 tokens
- Command speckit.spex-collab.revise A 23 tokens
- Command speckit.spex-collab.reconcile A 21 tokens
- Command speckit.spex-detach.detach A 18 tokens
- Command speckit.spex-collab.phase-split B 7 tokens
- Command update-superpowers C 16 tokens
What ships with it
1 file beside plugin.json 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 7a15ee2d3673
- 8d ago Changed a8432a189830
- 1mo ago First seen · 26 lines scan A 3816aad9d08b
spex is a plugin published in the GitHub repository rhuss/cc-spex (120 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins marketplace
Plugin marketplace listing 123 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
code-modernization
Guided modernization for any legacy codebase: start with /modernize, get an assessment, an interactive map, the business rules mined from the code, and a plan you approve, then an upgrade, a rewrite or a rebuild with independent proof that the new code behaves like the old. Includes security hardening, a one-page…