configure

configure is a command for coding agents from anthropics/claude-plugins-official. It costs 8 tokens per session (692 once invoked), scanned C, original, Apache-2.0.

An interactive command for enabling or disabling existing hookify rules, which are project files that watch for specified patterns.

In plain words
What is it for?
Use it to turn individual behavior checks on or off and review their current state.
Why use it?
It lets you change which safeguards are active without deleting or rewriting their configuration.

Command

Part of the hookify plugin — 1 skill, 4 commands, 1 agent shipped together

About the project

Claude Code Plugins Directory is a marketplace containing plugins for Claude Code, including tools, commands, skills, agents, hooks, and model context servers. Claude Code users browse it to install Anthropic-maintained or approved third-party extensions.

anthropics/claude-plugins-official · 35,867 stars · on GitHub

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/anthropics/claude-plugins-official/configure
Clone the repo
git clone --depth 1 https://github.com/anthropics/claude-plugins-official

Or install hookify, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 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 configure

README.md
[![agentmods](https://agentmods.dev/badge/commands/anthropics/claude-plugins-official/configure.svg)](https://agentmods.dev/commands/anthropics/claude-plugins-official/configure)
Your own site
<a href="https://agentmods.dev/commands/anthropics/claude-plugins-official/configure"><img src="https://agentmods.dev/badge/commands/anthropics/claude-plugins-official/configure.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 692 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00008 $0.00692
Opus 5 $0.00004 $0.00346
Sonnet 5 $0.00002 $0.00138
Haiku 4.5 $0.00001 $0.00069

Measured yesterday against content hash 1cb84c1055f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

configure 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 yesterday.

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.

"description": "Warns about rm -rf commands"
Origin

Copies of this mod

6 near-identical copies found in the catalogue:

plugins/hookify/commands/configure.md · 129 lines

How it starts

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

Configure Hookify Rules

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

Enable or disable existing hookify rules using an interactive interface.

Steps

1. Find Existing Rules

Use Glob tool to find all hookify rule files:

pattern: ".claude/hookify.*.local.md"

If no rules found, inform user:

No hookify rules configured yet. Use `/hookify` to create your first rule.

2. Read Current State

For each rule file:

  • Read the file
  • Extract name and enabled fields from frontmatter
  • Build list of rules with current state

3. Ask User Which Rules to Toggle

Use AskUserQuestion to let user select rules:

{
  "questions": [
    {
      "question": "Which rules would you like to enable or disable?",
      "header": "Configure",
      "multiSelect": true,
      "options": [
        {
          "label": "warn-dangerous-rm (currently enabled)",
          "description": "Warns about rm -rf commands"
        },
        {
          "label": "warn-console-log (currently disabled)",
          "description": "Warns about console.log in code"
        },
        {
          "label": "require-tests (currently enabled)",
          "description": "Requires tests before stopping"
        }
      ]
    }
  ]
}

Option format:

  • Label: {rule-name} (currently {enabled|disabled})
  • Description: Brief description from rule's message or pattern

4. Parse User Selection

For each selected rule:

  • Determine current state from label (enabled/disabled)
  • Toggle state: enabled → disabled, disabled → enabled

5. Update Rule Files

For each rule to toggle:

  • Use Read tool to read current content
  • Use Edit tool to change enabled: true to enabled: false (or vice versa)
  • Handle both with and without quotes

Edit pattern for enabling:

old_string: "enabled: false"
new_string: "enabled: true"

Edit pattern for disabling:

old_string: "enabled: true"
new_string: "enabled: false"

6. Confirm Changes

Read the full file on GitHub · 129 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. yesterday First seen · 129 lines · 8 tokens per session scan C 1cb84c1055f6

Subscribe to this mod's changes

configure is a command published in the GitHub repository anthropics/claude-plugins-official (35,867 stars, last pushed yesterday), licensed Apache-2.0. It adds 8 tokens to every session and 692 once invoked, about $0.0000 per session on Opus 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-09-03.