Repository navigation
v1.8.5
The last two packs now read rule first: agent-harness (agent-instructions, flight-deck, guardrail-hooks, handover, retro, windows-agent-shell) and agent-teams (claude-agents, codex-agents, grok-agents; delegation went first, in v1.8.1). Every section and rule opens with one bold sentence you can quote as it stands, and the dated stories behind the rules moved to a receipts.md beside each skill. With this release, all 44 skills read this way; work-humanizer already did.
Changed: guardrail-hooks' live check is a canary. Install step 4 and Re-verify now run true guard-canary and true user.email=<an address you blocked>. true does nothing, so nothing real runs whether or not a hook is wired, and the guard answers the canary whatever its rules. Never test a guard with a real one-way door: when the hook is not wired, it runs. Run the hooks' tests from the copy beside your installed hooks, python .claude/hooks/test_hooks.py, which now skips its own file.
The guard's limits, now stated: it matches what the shell runs and scans the scripts a command runs by path (python cleanup.py). It does not see python -c or node -e code, a script run after cd, ./script, python -m, uv run x.py or piped code, so a delete reached that way runs unasked. Say so where your instructions name the guard.
Also:
independent-review's wrapper andship-checksay to delete only untracked files the session generated, and otherwise to gitignore them or ask the owner.security-audit-staticandperformance-audit-staticno longer pre-approvegit log,git difforgit show: their--outputwrites a file.retropipes a sample into a hook instead of running a real command.
What to do:
- If you installed
guardrail-hooks' scripts: copy the newguard_one_way_doors.pyandtest_hooks.pyover your copies, keeping your rules, and run the canary. - If you copied any of these skills into your repository: copy its
receipts.mdwith it.
Install: README § Install. Lost at any point? Type /product:start-here (Codex: $product:start-here) and say what you have.