AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Cccc

skill-jtropy-cccc-skill-cccc · by JTropy

Use when the user explicitly requests cccc/4C, asks to launch local Claude Code or Codex as a peer, or confirms a suggested local peer handoff for bounded implementation or a read-only second opinion. Do not use when the user or project rules prohibit external agents.

No reviews yet
0 installs
27 views
0.0% view→install

Install

$ agentstack add skill-jtropy-cccc-skill-cccc

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-jtropy-cccc-skill-cccc)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Cccc? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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 delegate or consult terms 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](references/setup.md) 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 0 as the success authority; an existing report or opinion alone is not success.
  • DELEGATE_DEPTH and 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.

6. Load only the chosen workflow

  • For implementation, read [delegate workflow](references/delegate.md).
  • For a second opinion, read [consult workflow](references/consult.md).
  • For installation, migration, authentication, or optional capability checks, read [setup](references/setup.md).
  • After a failed wrapper run, read [troubleshooting](references/troubleshooting.md).

Do not preload every reference. The selected workflow contains its card, invocation, and result checks.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.