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 skills add anthony-spruyt/claude-plugins --skill configuregit clone --depth 1 https://github.com/anthony-spruyt/claude-pluginsWrote 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.
[](https://agentmods.dev/skills/anthony-spruyt/claude-plugins/configure)<a href="https://agentmods.dev/skills/anthony-spruyt/claude-plugins/configure"><img src="https://agentmods.dev/badge/skills/anthony-spruyt/claude-plugins/configure.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00041 | $0.00655 |
| Opus 5 | $0.00020 | $0.00328 |
| Sonnet 5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
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 7d 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.
"description": "Warns about rm -rf commands" How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure Hookify Rules
Load the hookify-plus:writing-rules skill first to understand rule format.
Enable or disable existing hookify rules via an interactive selection interface.
Steps
1. Find Existing Rules
Use Glob tool to find all hookify rule files:
pattern: ".claude/hookify-plus/*.md"
If no rules found, inform the 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
nameandenabledfields from frontmatter - Build a list of rules with current state
3. Present Interactive Selection
Use AskUserQuestion to let the user select rules to toggle:
{
"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"
}
]
}
]
}
Format each option as:
- Label:
{rule-name} (currently {enabled|disabled}) - Description: Brief summary from the rule's message or pattern
4. Parse Selection and Toggle
For each selected rule, determine its current state from the label and invert it: enabled becomes disabled, disabled becomes enabled.
5. Update Rule Files
Read each rule file with the Read tool, then use the Edit tool to flip the enabled frontmatter field. Handle both quoted and unquoted values.
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
Display a summary of what changed:
## Hookify Rules Updated
**Enabled:**
- warn-console-log
**Disabled:**
- warn-dangerous-rm
**Unchanged:**
- require-tests
Changes apply immediately - no restart needed.
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.
- 7d ago First seen · 116 lines · 41 tokens per session scan C cdef77c748f3
configure is a skill published in the GitHub repository anthony-spruyt/claude-plugins (2 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 655 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…