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 commands/husniadil/cc-hooks/updategit clone --depth 1 https://github.com/husniadil/cc-hooksWhat 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.00009 | $0.01550 |
| Opus 5 | $0.00005 | $0.00775 |
| Sonnet 5 | $0.00002 | $0.00310 |
| Haiku 4.5 | $0.00001 | $0.00155 |
Grade B, and why
update scanned grade B with 2 findings 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 3d 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.
settings_file = os.path.expanduser('~/.claude/settings.json') Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:12222/version/status 2>/dev/null || \ How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cc-hooks Update Assistant
Check for cc-hooks updates and install them if available.
Update Check Flow
1. Detect Installation Mode
Determine if cc-hooks is running in plugin mode or standalone mode by checking the hooks configuration:
# Detect installation mode
python3 -c "
import json, sys, os
# Check 1: Plugin mode - hooks defined in plugin directory
plugin_hooks_file = os.path.expanduser('~/.claude/plugins/marketplaces/cc-hooks-plugin/hooks/hooks.json')
if os.path.isfile(plugin_hooks_file):
try:
with open(plugin_hooks_file, 'r') as f:
config = json.load(f)
# Verify it has hooks configuration
if config.get('hooks') and len(config['hooks']) > 0:
# Verify hooks.py exists
plugin_hooks_py = os.path.expanduser('~/.claude/plugins/marketplaces/cc-hooks-plugin/hooks.py')
if os.path.isfile(plugin_hooks_py):
print('plugin')
sys.exit(0)
except:
pass
# Check 2: Standalone mode - hooks defined in settings.json
settings_file = os.path.expanduser('~/.claude/settings.json')
if os.path.isfile(settings_file):
try:
with open(settings_file, 'r') as f:
config = json.load(f)
hooks = config.get('hooks', {})
# Check if any hook points to hooks.py
for event_hooks in hooks.values():
if isinstance(event_hooks, list):
for matcher_group in event_hooks:
for hook in matcher_group.get('hooks', []):
command = hook.get('command', '')
if 'hooks.py' in command:
print('standalone')
sys.exit(0)
except:
pass
print('unknown')
"
Detection Logic:
- Check Plugin Mode First:
- Look for
~/.claude/plugins/marketplaces/cc-hooks-plugin/hooks/hooks.json - Verify it contains valid
hooksconfiguration - Verify
hooks.pyexists at~/.claude/plugins/marketplaces/cc-hooks-plugin/hooks.py - If all checks pass → Plugin mode
- Look for
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.
- 3d ago First seen · 252 lines · 9 tokens per session scan B 43013081262d
update is a command published in the GitHub repository husniadil/cc-hooks (19 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 1,550 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
derive-tests
Turn documented intent into a test-coverage map — inventory the tests that exist today, derive use-case cases from the system docs, separate existing coverage from proposed tests and unverified gaps, mark each unit / guarded-live / manual, and recommend a green-before-merge CI gate.
ship-check
Turn a vibe-coded repo into a reviewer-ready shipping packet — document the app, wire agent context, run security and performance audits, map test coverage, and compile the results.
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.
plan-launch
Create a full go-to-market strategy — beachhead segment, ICP, messaging, channels, and launch plan.
competitive-analysis
Analyze the competitive landscape — identify competitors, compare strengths and weaknesses, find differentiation opportunities.
video
Video projects - list, resume, or create new.