setup

A setup assistant for configuring the cc-hooks plugin and its command-line shortcuts. It checks whether uv and the cld shell alias are available.

In plain words
What is it for?
Checking uv, detecting the current shell, checking cld aliases in common shell configuration files, and guiding alias setup.
Why use it?
It helps identify missing prerequisites and configuration, reducing setup errors before you use the plugin.

Command

Install

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.

agentmods
npx agentmods add commands/husniadil/cc-hooks/setup
Clone the repo
git clone --depth 1 https://github.com/husniadil/cc-hooks
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,706 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 3 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00006 $0.03706
Opus 5 $0.00003 $0.01853
Sonnet 5 $0.00001 $0.00741
Haiku 4.5 $0.00001 $0.00371

Measured 2d ago against content hash 98858b94c603, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

setup scanned grade D with 3 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 2d 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

- **macOS/Linux**: `curl -LsSf https://astral.sh/uv/install.sh | sh`

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat ~/.claude/settings.json | grep -A 2 '"statusLine"'

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- **macOS/Linux**: `curl -LsSf https://astral.sh/uv/install.sh | sh`
commands/setup.md · 494 lines

How it starts

The opening of the file, as written. The whole thing — 494 lines — stays where its author put it; the contents beside it link to each section on GitHub.

cc-hooks Setup Assistant

Help the user set up and configure the cc-hooks plugin. Follow these steps:

1. System Requirements Check

Check if uv is installed:

uv --version

If not installed, guide the user to install it:

  • macOS/Linux: curl -LsSf https://astral.sh/uv/install.sh | sh
  • Windows: powershell -c "irm https://astral.sh/uv/install.ps1 | iex"

2. Shell Alias Setup

2.1. Check cld Alias Availability

Check if cld command is available using BOTH methods:

# Detect user's shell
echo $SHELL

# Method 1: Test if cld works in current shell
type cld 2>/dev/null && echo "cld: available in current shell" || echo "cld: not found in current shell"

# Method 2: Check if cld is configured in shell config files
grep -h "alias cld=" ~/.zshrc ~/.bashrc ~/.bash_profile ~/.profile 2>/dev/null && echo "cld: found in shell config" || echo "cld: not found in shell config"

Decision logic:

  • If EITHER method finds cld → Skip to checking wrapper alias (Section 2.2)
  • If BOTH methods fail → Offer to create cld alias

Creating cld Alias (only if not found)

If cld is not available in either current shell or config files, guide the user to add it:

For zsh users (~/.zshrc):

alias cld='~/.claude/plugins/marketplaces/cc-hooks-plugin/claude.sh'

For bash users (~/.bashrc or ~/.bash_profile):

alias cld='~/.claude/plugins/marketplaces/cc-hooks-plugin/claude.sh'

Ask the user if they would like to add the cld alias to their shell configuration for convenience.

If the user agrees, add the appropriate alias to their shell config file and remind them to run source ~/.zshrc (or appropriate config file) or restart their terminal.

2.2. Check for Wrapper Alias (Optional)

After confirming cld is available (either in current shell or config files), check if a wrapper alias already exists:

# Check for any alias that wraps cld with arguments
grep -h "alias.*='cld " ~/.zshrc ~/.bashrc ~/.bash_profile ~/.profile 2>/dev/null | grep -v "^#"

Read the full file on GitHub · 494 lines

Changes

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.

  1. 2d ago First seen · 494 lines · 6 tokens per session scan D 98858b94c603

Subscribe to this mod's changes

setup is a command published in the GitHub repository husniadil/cc-hooks (19 stars, last pushed 6mo ago), licensed MIT. It adds 6 tokens to every session and 3,706 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it D with 3 findings (downloads and executes remote code, 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.