help

help is a skill for Claude Code from anthony-spruyt/claude-plugins. It costs 56 tokens per session (885 once invoked), scanned C, original, MIT.

A help guide for Hookify, a plugin that runs checks when an agent uses tools or receives prompts. It explains how simple Markdown files can define rules that warn about unwanted actions.

In plain words
What is it for?
Use it to learn which events are available, where rule files go, and how to create warnings for commands, file changes, prompts, or stopping actions.
Why use it?
It removes the need to understand Hookify's hook events and configuration structure before creating safeguards for an agent.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: reads .claude/ paths; mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the hookify-plus plugin — 5 skills, 1 agent shipped together

Good fit Use it to learn which events are available, where rule files go, and how to create warnings for commands, file changes, prompts, or stopping actions.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add anthony-spruyt/claude-plugins
Claude Code
/plugin install hookify-plus

Made for: Claude Code.

Or install hookify-plus, the plugin that ships this one along with the rest of its 5 skills, 1 agent.

Wrote 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.

agentmods badge for help

README.md
[![agentmods](https://agentmods.dev/badge/skills/anthony-spruyt/claude-plugins/help/github.svg)](https://agentmods.dev/skills/anthony-spruyt/claude-plugins/help)
Your own site
<a href="https://agentmods.dev/skills/anthony-spruyt/claude-plugins/help"><img src="https://agentmods.dev/badge/skills/anthony-spruyt/claude-plugins/help/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for help

Your own site · 80×15
<a href="https://agentmods.dev/skills/anthony-spruyt/claude-plugins/help"><img src="https://agentmods.dev/badge/skills/anthony-spruyt/claude-plugins/help.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 885 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00056 $0.00885
Opus 5.5 $0.00022 $0.00354
Sonnet 5.5 $0.00011 $0.00177
Haiku 4.5 $0.00006 $0.00089

Measured 17d ago against content hash 1034f75ba86d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

help scanned grade C 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 17d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

/hookify Warn me when I try to use rm -rf
hookify-plus/skills/help/SKILL.md · 117 lines

How it starts

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

Hookify Plugin Help

Explain how the hookify plugin works and how to use it.

Overview

The hookify plugin makes it easy to create custom hooks that prevent unwanted behaviors. Instead of editing hooks.json files, create simple markdown configuration files that define patterns to watch for.

How It Works

Hook System

Hookify installs generic hooks that run on these events:

  • PreToolUse: Before any tool executes (Bash, Edit, Write, etc.)
  • PostToolUse: After a tool executes
  • Stop: When Claude wants to stop working
  • UserPromptSubmit: When user submits a prompt

These hooks read rule files from .claude/hookify-plus/*.md (project), ~/.claude/hookify-plus/*.md (global), and <sibling_plugin>/hookify-plus/*.md (plugins in the same marketplace), and check if any rules match the current operation.

Configuration Files

Create rules as .md files in the .claude/hookify-plus/ directory:

---
name: warn-dangerous-rm
enabled: true
event: bash
pattern: rm\s+-rf
---

Warning: Dangerous rm command detected!

This command could delete important files. Verify the path.

Key fields:

  • name: Unique identifier for the rule
  • enabled: true/false to activate/deactivate
  • event: bash, file, read, stop, prompt, or all
  • pattern: Regex pattern to match (case-insensitive)
  • warn_once: Only warn once per agent (main thread and each subagent) (optional)
  • warn_interval: Warn every N matches; 0 = every time (optional)

The message body is what Claude sees when the rule triggers.

Creating Rules

Option A: Use /hookify command

/hookify Don't use console.log in production files

This analyzes the request and creates the appropriate rule file.

Option B: Create manually

Create .claude/hookify-plus/my-rule.md with the format above.

Option C: Analyze conversation

/hookify

Without arguments, hookify analyzes recent conversation to find behaviors to prevent.

Available Commands

  • /hookify - Create hooks from conversation analysis or explicit instructions
  • /hookify-plus:help - Show this help
  • /hookify-plus:list - List all configured hooks
  • /hookify-plus:configure - Enable/disable existing hooks interactively

Read the full file on GitHub · 117 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 17d ago Changed 1034f75ba86d
  2. 22d ago Changed bf6d2cf945e5
  3. 1mo ago First seen · 117 lines · 56 tokens per session scan C dbb90b33522d

Subscribe to this mod's changes

help is a skill published in the GitHub repository anthony-spruyt/claude-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 885 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens