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/jtropy/cccc-skill/ccccnpx skills add JTropy/cccc-skill --skill ccccgit clone --depth 1 https://github.com/JTropy/cccc-skillWhat 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.00058 | $0.00682 |
| Opus 5 | $0.00029 | $0.00341 |
| Sonnet 5 | $0.00012 | $0.00136 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
cccc 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cccc
Route one bounded request to the other installed local CLI. delegate permits scoped implementation; consult requests a read-only second opinion. The orchestrator validates the result and makes no unverified capability claim.
1. Authorization gate
- An explicit request naming cccc/4C, this wrapper, or a handoff to the installed local Claude Code or Codex peer authorizes that path within the user's scope.
- Bare
delegateorconsultterms are not launch authorization; treat them as a heuristic until the user confirms the local peer handoff. - For a heuristic match, only suggest cccc. Confirm with the user before any external CLI launch.
- If user or project instructions prohibit external agents, do not launch a wrapper.
Discovery of this skill is not launch authorization. Apply this gate again immediately before invoking a wrapper.
2. Routing precedence
Use this order exactly:
user instruction > project rules > verified local capability > heuristic
The Codex orchestrator targets Claude; the Claude Code orchestrator targets Codex. Never target itself or infer identity from executable availability.
3. Choose one channel
| Need | Channel | Result |
|---|---|---|
| Bounded repository implementation with explicit editable paths | delegate |
Peer changes plus a report and audit log |
| Analysis, critique, or decision support without repository edits | consult |
Peer opinion plus an audit log |
Do not use consult as authorization to implement its recommendation. Do not use delegate when the user asked only for analysis.
4. Verify capability
Verify the selected CLI and authentication before launch. Follow setup when a check fails.
For raster images, verify usable Codex $imagegen capability first. Do not promise image generation, a model, effort, cost, or network path.
5. Safety invariants
- Use only the canonical wrappers in this skill. Never construct a looser raw CLI fallback.
- Treat wrapper exit status
0as the success authority; an existing report or opinion alone is not success. DELEGATE_DEPTHand wrapper prompts guard against accidental peer recursion; do not ask the peer to invoke another agent.- Tool restrictions limit exposed operations. The post-run Git audit detects Git-visible changes; neither control is an OS sandbox. Use external isolation for an untrusted repository.
- The peer must not alter repository history, hide working state, discard files, publish changes, or broaden the requested scope.
What ships with it
13 files beside SKILL.md 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.
- agents/openai.yaml 211 B
- assets/discussion-card.md 676 B
- assets/task-card.md 893 B
- references/consult.md 3.5 KB
- references/delegate.md 3.8 KB
- references/setup.md 4.0 KB
- references/troubleshooting.md 4.0 KB
- scripts/cccc-common.sh 24 KB runs code
- scripts/consult.sh 66 KB runs code
- scripts/delegate.sh 50 KB runs code
- scripts/publish-no-clobber.py 20 KB runs code
- scripts/run-with-timeout.py 48 KB runs code
- scripts/windows-exec-argv.sh 1.3 KB runs code
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 · 58 lines · 58 tokens per session scan A 1fe8dbfe3f94
cccc is a skill published in the GitHub repository JTropy/cccc-skill (10 stars, last pushed 20d ago), licensed MIT. It adds 58 tokens to every session and 682 once invoked, about $0.0003 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-31.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.