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.
/plugin marketplace add john-farina/claude-plugins/plugin install conjureWrote 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/commands/john-farina/claude-plugins/conjure-hook)<a href="https://agentmods.dev/commands/john-farina/claude-plugins/conjure-hook"><img src="https://agentmods.dev/badge/commands/john-farina/claude-plugins/conjure-hook/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.
<a href="https://agentmods.dev/commands/john-farina/claude-plugins/conjure-hook"><img src="https://agentmods.dev/badge/commands/john-farina/claude-plugins/conjure-hook.svg" alt="Reviewed on agentmods" width="80" 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.00032 | $0.03864 |
| Opus 5.5 | $0.00013 | $0.01546 |
| Sonnet 5.5 | $0.00006 | $0.00773 |
| Haiku 4.5 | $0.00003 | $0.00386 |
Grade B, and why
conjure-hook scanned grade B 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/conjure-config.md 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 0: Route the Request
Before building anything, verify a hook is the right artifact.
| Question | If YES → use instead |
|---|---|
Does the user trigger this explicitly via /command? |
Skill → run /conjure-skill <name> |
| Does Claude spawn this with isolated context or a different model? | Agent → run /conjure-agent <description> |
| Should this fire automatically on an event without the user asking? | Hook → continue ✅ |
Common mislabels:
| Request sounds like… | Actually is… |
|---|---|
| "hook to commit my changes" | Skill — user-triggered |
| "hook to search the codebase" | Agent — isolated, spawned by Claude |
| "hook that fires whenever I edit a file" | Hook ✅ |
| "hook that runs on session start" | Hook ✅ |
| "hook to review my PR" | Skill — user-triggered workflow |
If it's clearly a skill or agent, stop and say: "This is better as a [skill/agent] — run /conjure-skill or /conjure-agent instead."
Phase 0.5: Load User Preferences
Before doing anything else, read both conjure config files if they exist:
cat ~/.claude/conjure-config.md 2>/dev/null
cat .claude/conjure-config.md 2>/dev/null
Follow all instructions found in ## hooks and ## global sections throughout every phase of this command. Project-local instructions (.claude/conjure-config.md) take precedence over global ones when they conflict. If neither file exists, proceed with defaults.
Phase 1: Parse Arguments + Detect Mode
Parse $ARGUMENTS:
| Pattern | Mode |
|---|---|
| empty | Create — ask what the hook should do |
| description only (no slug) | Create — use description as intent |
<slug> only, found in settings.json |
Update — read entry + script, refine |
<slug> only, not found |
Create — use slug as intended name |
<slug> review |
Review — audit script + settings entry, report issues |
<slug> add-event |
Extend — add a new event to an existing hook's script |
help |
Stop and print the Phase 1 argument table above, then stop |
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.
- 1mo ago First seen · 375 lines · 32 tokens per session scan B 68eec6a9c194
conjure-hook is a command published in the GitHub repository john-farina/claude-plugins (1 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 3,864 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
strip
This is the task-based stripper, not the always-on prior: a deliberate cleanup pass you asked for. Apply the fp-minify doctrine to the target and remove or compress comments that don't earn their place.
web-design
Design and build a complete website or webapp from a project brief — end-to-end workflow from design to working React/Vite code.
design
Create a design direction and styleguide for a project — produces aesthetic direction, fonts, colors, imagery, and media prompts.
media-generate
Generate a media asset — image, video, music, or speech — with guided prompts and sensible defaults.
media-assets
List, organize, and manage generated media assets in the output directory.
permissions
Create or update DOGMA-PERMISSIONS.md to configure what Claude can do autonomously.