KevinZai $ccc-safety — Safety
The guardrails deck. CC Commander's hooks already journal every permission decision (~/.claude/commander/analytics/permission-gate.jsonl) and every tool failure (~/.claude/commander/tool-failures.jsonl). This turns them into one page: how many dangerous actions got blocked, how many were auto-fixed, and which tools/errors trip you up most (a Sniffly-style breakdown).
🔒 Privacy: read locally. Publishing uploads the artifact (counts, tool names, redacted error signatures) to your private claude.ai artifact URL — private to your account, but it leaves the machine. Always ask before publishing; never publish automatically. Error text is redacted (sk-/Bearer/token patterns → [redacted]) before it ever reaches the page.
How it routes
On $ccc-safety with no argument, open a click-first picker:
AskUserQuestion:
question: "Safety — how do you want it?"
options:
- 🛰️ Publish the deck — a living Safety artifact: blocked actions, auto-fixes, failure hotspots
- 🗣️ Plain-English status — narrate the headline numbers here, no jargon
$ccc-safety open (or snapshot) → publish the deck. $ccc-safety status → narrate.
Zero-state: if permission-gate.jsonl and tool-failures.jsonl are both missing/empty, say so plainly — "No guardrail activity logged yet — the hooks fill this in as you work." Never render an error for an empty deck.
🛰️ Publish the deck
LIVING PATTERN: always render to the SAME file path (scratchpad/ccc-safety-live.html), then republish that same path with the Artifact tool — same path, same URL, one living page. Do not change this path — it is the identity of every bookmark anyone already has for this deck.
Since v7.4.0 this page is the Safety tab of the Commander Console, published on its own — one builder renders every deck and the console, so the numbers can't disagree:
mkdir -p scratchpad
if [ -f "${CLAUDE_PLUGIN_ROOT}/scripts/build-console.mjs" ]; then
node "${CLAUDE_PLUGIN_ROOT}/scripts/build-console.mjs" \
--surface artifact --tab safety --out scratchpad/ccc-safety-live.html
else
node commander/cowork-plugin/scripts/build-console.mjs \
--surface artifact --tab safety --out scratchpad/ccc-safety-live.html
fi
The page is unchanged apart from one added line pointing at $ccc-console (the inline all-in-one view).
First publish this session → ask before publishing (counts, tool names, redacted error signatures leave the machine for your private artifact URL). Every later run of $ccc-safety → invoking the skill again IS the refresh consent: republish the same file path to the same URL without re-asking. Publish scratchpad/ccc-safety-live.html with the Artifact tool (favicon 🛡️). End with the artifact title + the headline: "blocked N dangerous actions, auto-fixed M." To refresh later: run $ccc-safety again — same URL updates in place; viewers reload.
🗣️ Plain-English status
Run readSafetyModel({}) and read the decision counts + top failing tool, then narrate caveman-simple: "Commander stopped N risky actions and quietly fixed M. Your Bash commands fail most — usually timeouts." No jargon.
The deck also links the others
The published artifact carries the shared Commander decks strip at the top — one click (copy) away from the Cockpit, Mission Control, and Usage & Cost decks. Users always know the other decks exist. It also carries one line pointing at $ccc-console, the inline console that shows all of these tabs at once (and has a prompt bar, which a published page cannot).
On Codex: some panels may be empty on Codex today — Safety's failure hotspots, Mission Control's agent roster, and Usage's savings hero are fed from Claude-only hooks right now. A follow-up workstream wires the matching Codex telemetry.
⚙️ Fable contract: plan before build · verifier ≠ worker · prove before alarm · loops need gates · leave durable state —
rules/fable-method.md
(On Codex, present these options as a numbered list and ask the user to reply with a number — AskUserQuestion is Claude-only.)