setup-hooks
Install CAS safety hooks into your Claude Code settings. Hooks intercept dangerous commands, secret access, and git pushes — prompting you before proceeding.
What this skill does
You are the CAS Hooks installer. Your job is to verify that CAS safety hooks are active and clean up any legacy manual installations.
## How CAS Hooks Work (v7.17+)
CAS hooks are now **automatic** — they activate via the plugin's `hooks/hooks.json` when the CAS plugin is enabled. No manual setup is needed.
Three PreToolUse hooks ship with the plugin:
| Hook | Matcher | What it catches |
|------|---------|----------------|
| **push-guard** | `Bash` | Any `git push` or `gh pr create` — commits are allowed freely |
| **dangerous-commands** | `Bash` | `rm -rf ~/`, `dd` to disk, `git reset --hard`, `curl \| sh`, fork bombs, etc. |
| **protect-secrets** | `Read\|Edit\|Write\|Bash` | `.env` files, SSH keys, AWS creds, secret variables, exfiltration attempts |
All hooks log to `~/.claude/hooks-logs/` for audit trail.
## Steps
### Step 1: Verify plugin is enabled
Check `~/.claude/settings.json` for `"cas@claude-agent-system": true` in `enabledPlugins`. If not enabled, tell the user to run `/plugin install cas` first.
### Step 2: Clean up legacy manual hooks
**IMPORTANT**: Older CAS versions (pre-7.17) required manual installation that hardcoded version-specific paths like:
```
node ~/.claude/plugins/cache/claude-agent-system/cas/7.0.0/hooks/push-guard.js
```
These break on every plugin update because the old cache version gets purged.
Read `~/.claude/settings.json` and look for any `PreToolUse` hooks whose `command` field contains:
- `plugins/cache/claude-agent-system/cas/` (hardcoded cache paths)
- `push-guard.js`, `dangerous-commands.js`, or `protect-secrets.js` with absolute versioned paths
**Remove these entries** from the `hooks.PreToolUse` array — they are now handled automatically by the plugin's `hooks/hooks.json` using `${CLAUDE_PLUGIN_ROOT}` which always resolves to the current version.
⚠️ Only remove CAS hook entries. Do NOT remove the user's other hooks (notification hooks, custom hooks, etc.).
### Step 3: Confirm
Display:
```
CAS Safety Hooks — Status
═════════════════════════
✅ Plugin hooks active (automatic via hooks.json):
• push-guard — prompts before git push
• dangerous-commands — prompts before destructive commands
• protect-secrets — prompts before accessing secrets
🧹 Legacy cleanup: [removed N old manual entries / no legacy entries found]
Hooks use "ask" mode — Claude will prompt you for approval.
Logs: ~/.claude/hooks-logs/
```
## Important Rules
- NEVER remove non-CAS hooks from settings.json
- NEVER modify the hook scripts themselves
- If `~/.claude/settings.json` has other config (permissions, env, etc.), preserve it all
- The plugin's hooks.json uses `${CLAUDE_PLUGIN_ROOT}` which auto-resolves — no version numbers needed
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.