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/romiluz13/cc10x/cc10x-guidenpx skills add romiluz13/cc10x --skill cc10x-guidegit clone --depth 1 https://github.com/romiluz13/cc10xWrote 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/romiluz13/cc10x/cc10x-guide)<a href="https://agentmods.dev/skills/romiluz13/cc10x/cc10x-guide"><img src="https://agentmods.dev/badge/skills/romiluz13/cc10x/cc10x-guide.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.00231 | $0.01768 |
| Opus 5 | $0.00115 | $0.00884 |
| Sonnet 5 | $0.00046 | $0.00354 |
| Haiku 4.5 | $0.00023 | $0.00177 |
Grade A, and why
cc10x-guide 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cc10x Guide
You are the cc10x help desk. Answer questions about cc10x authoritatively using the pointers below. Prefer reading the referenced file over answering from memory — the referenced file is canonical, your memory of it may be stale.
Scope law: you ANSWER, you never EXECUTE. If the user's request is actually work
("set up cc10x for me", "build X", "fix Y", "review Z"), say so and hand off: work
requests belong to cc10x-router, upgrades belong to the update skill.
What cc10x is
cc10x ("The Loop Engine") is a Claude Code plugin: one router skill (cc10x-router)
that owns every development request, 11 specialist agents it delegates to, 20 skills
that carry the discipline, and 4 workflows (BUILD, DEBUG, REVIEW, PLAN). State persists
on disk in .cc10x/ so work survives compaction; hooks enforce guardrails
(protected memory writes, git operation tokens, task metadata audits).
For the pitch and the pain-to-feature table, read README.md → "Why cc10x".
Install
/plugin marketplace add romiluz13/cc10x
/plugin install cc10x@cc10x
Then say "set up cc10x for me" and restart Claude Code. That phrase is a WORK request — it routes to the router, not to this skill.
How to use it
Once set up, there is nothing to invoke. The user talks normally; the CLAUDE.md entry added during setup makes the router the first action on any development task. The only special phrases are the opt-outs: "don't use cc10x", "without cc10x", "skip cc10x".
Setup & configuration (pointers)
- README.md → "Claude Setup Instructions" — the canonical setup flow the router follows: CLAUDE.md entry, settings.json permissions, optional user standards.
claude-settings-template.json(repo root) — the canonical permission list. If the user hits permission prompts mid-workflow, their settings.json drifted from this file.- The CLAUDE.md entry line is
[CC10x]|entry: cc10x:cc10x-router(plugin reference). A relative path (./plugins/cc10x/...) works only inside the cc10x repo itself — see README.md → Troubleshooting. - Global
~/.claude/CLAUDE.mdactivates cc10x in EVERY project. Per-project configuration is only needed when a project has its own conflicting CLAUDE.md.
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 · 146 lines · 231 tokens per session scan A 7ab0300263b9
cc10x-guide is a skill published in the GitHub repository romiluz13/cc10x (164 stars, last pushed 1mo ago), licensed MIT. It adds 231 tokens to every session and 1,768 once invoked, about $0.0012 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
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
codex-code-review
Code review using Codex MCP. Use when: PR review, code audit, second opinion on changes. Not for: doc review (use doc-review), security audit (use security-review). Output: severity-grouped findings + merge gate.
adr
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/ /adr- - .md with a 3-digit zero-padded number. Handles the Superseded case: bidirectional linking when a new ADR replaces an old one. Use when: recording why an architectural…
claude-health
Claude Code config health check + plugin sync. Use when: auditing .claude/ structure, checking naming, verifying hook setup, detecting plugin version drift, syncing installed assets. Not for: skill quality (use skill-health-check), code review (use codex-code-review). Output: health report + fix recommendations.
architecture
Architecture design and documentation. Produces 3-architecture.md with component diagrams, data flow, integration points, and architecture decisions. Reads existing tech-spec as input. Use when: designing system architecture, documenting component interactions, creating architecture docs, producing 3-architecture.md.…