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/kasempiternal/claude-agent-system/setup-hooksnpx skills add Kasempiternal/Claude-Agent-System --skill setup-hooksgit clone --depth 1 https://github.com/Kasempiternal/Claude-Agent-SystemWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/kasempiternal/claude-agent-system/setup-hooks)<a href="https://agentmods.dev/skills/kasempiternal/claude-agent-system/setup-hooks"><img src="https://agentmods.dev/badge/skills/kasempiternal/claude-agent-system/setup-hooks.svg" alt="Measured on agentmods" height="20"></a>What 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.00027 | $0.00932 |
| Opus 5 | $0.00014 | $0.00466 |
| Sonnet 5 | $0.00005 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade B, and why
setup-hooks scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Read `~/.claude/settings.json` and confirm `enabledPlugins["cas@claude-agent-system"]` is `true`. How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CAS Safety Hooks
Verify the current CAS hook contract. The plugin owns its hooks through ${CLAUDE_PLUGIN_ROOT}; no version-pinned manual installation is required.
Intended behavior
| Guard | Tool matcher | Decision |
|---|---|---|
| Secret and environment protection | `Read | Edit |
| Sensitive command approval | Bash |
Ask for every rm, git commit, git commit-tree, or git push, including common wrappers and nested shell commands |
| GPT Architect backend guard | Agent |
While GPT Architect is ON, deny native Claude teammates and direct delegation to Codex instead |
Ordinary builds, tests, formatters, package managers, file edits, and non-sensitive shell commands must remain automatic. The broad legacy dangerous-commands.js and push-guard.js hooks are retired and no longer ship.
Procedure
1. Verify the plugin
Read ~/.claude/settings.json and confirm enabledPlugins["cas@claude-agent-system"] is true.
If it is not enabled, stop and tell the user to run:
/plugin marketplace add Kasempiternal/Claude-Agent-System
/plugin install cas
2. Verify automatic hook registration
Locate the active CAS plugin root, read hooks/hooks.json, and verify these commands are registered exactly once:
protect-secrets.jssensitive-command-approval.cjsgpt-architect-mode-guard.cjsgpt-architect-standing-orders.cjs
Also verify orchestrate-resume.js remains the sole CAS SessionStart hook and gpt-architect-standing-orders.cjs the sole CAS UserPromptSubmit hook.
Do not add a second user-level copy of an automatic plugin hook.
3. Find obsolete manual entries
Inspect only hooks.PreToolUse entries in ~/.claude/settings.json. Mark an entry as obsolete when its command contains any of:
plugins/cache/claude-agent-system/cas/push-guard.jsdangerous-commands.jsprotect-secrets.jsclaude-sensitive-command-approval.cjssensitive-command-approval.cjsgpt-architect-native-agent-guard.cjsgpt-architect-mode-guard.cjsgpt-architect-standing-orders.cjs
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.
- 4d ago First seen · 101 lines · 27 tokens per session scan B 08f2b263f02b
setup-hooks is a skill published in the GitHub repository Kasempiternal/Claude-Agent-System (15 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 932 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
codex-test-gen
Generate unit tests for specified functions using Codex MCP.
ensure-pipelines-host
Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host…