list

list is a skill for Claude Code, Codex from anthony-spruyt/claude-plugins. It costs 43 tokens per session (581 once invoked), scanned A, original, MIT.

A tool for showing Hookify rules configured in a project. These rules are checks that can warn about matching commands, files, or events.

In plain words
What is it for?
Use it to see which rules exist, which are enabled, and where to edit them.
Why use it?
It gives you one view of each rule's name, status, trigger, pattern, message preview, and file location.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

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

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 skills/anthony-spruyt/claude-plugins/list
Any agent
npx skills add anthony-spruyt/claude-plugins --skill list
Clone the repo
git clone --depth 1 https://github.com/anthony-spruyt/claude-plugins

Made for: Claude Code, Codex.

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

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 list

README.md
[![agentmods](https://agentmods.dev/badge/skills/anthony-spruyt/claude-plugins/list.svg)](https://agentmods.dev/skills/anthony-spruyt/claude-plugins/list)
Your own site
<a href="https://agentmods.dev/skills/anthony-spruyt/claude-plugins/list"><img src="https://agentmods.dev/badge/skills/anthony-spruyt/claude-plugins/list.svg" alt="Measured on agentmods" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 581 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.00043 $0.00581
Opus 5 $0.00022 $0.00291
Sonnet 5 $0.00009 $0.00116
Haiku 4.5 $0.00004 $0.00058

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

Security

Grade A, and why

list scanned grade A with 0 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 5d 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

hookify-plus/skills/list/SKILL.md · 89 lines

What it actually says

List Hookify Rules

Load hookify-plus:writing-rules skill first to understand rule format.

Display all configured hookify rules in the project.

Steps

  1. Use Glob tool to find all hookify rule files:

    pattern: ".claude/hookify-plus/*.md"
    
  2. For each file found:

    • Read the file with the Read tool.
    • Extract frontmatter fields: name, enabled, event, pattern.
    • Extract message preview (first 100 chars).
  3. Present results in a table:

## Configured Hookify Rules

| Name | Enabled | Event | Pattern | File |
|------|---------|-------|---------|------|
| warn-dangerous-rm | ✅ Yes | bash | rm\s+-rf | dangerous-rm.md |
| warn-console-log | ✅ Yes | file | console\.log\( | console-log.md |
| check-tests | ❌ No | stop | .* | require-tests.md |

**Total**: 3 rules (2 enabled, 1 disabled)
  1. For each rule, show a brief preview:
### warn-dangerous-rm
**Event**: bash
**Pattern**: `rm\s+-rf`
**Message**: "⚠️ **Dangerous rm command detected!** This command could delete..."

**Status**: ✅ Active
**File**: .claude/hookify-plus/dangerous-rm.md
  1. Add helpful footer:
---

To modify a rule: Edit the `.md` file in `.claude/hookify-plus/` directly
To disable a rule: Set `enabled: false` in frontmatter
To enable a rule: Set `enabled: true` in frontmatter
To delete a rule: Remove the `.md` file from `.claude/hookify-plus/`
To create a rule: Use `/hookify` command

**Remember**: Changes take effect immediately - no restart needed

If No Rules Found

If no hookify rules exist, display:

## No Hookify Rules Configured

No hookify rules created yet.

To get started:
1. Use `/hookify` to analyze conversation and create rules
2. Or manually create `.claude/hookify-plus/my-rule.md` files
3. See `/hookify:help` for documentation

Example:

/hookify Warn me when I use console.log


Check `${CLAUDE_PLUGIN_ROOT}/examples/` for example rule files.
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. 5d ago First seen · 89 lines · 43 tokens per session scan A d13f746d8ea5

Subscribe to this mod's changes

list is a skill published in the GitHub repository anthony-spruyt/claude-plugins (2 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 581 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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