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 agentmods add commands/john-farina/claude-plugins/conjure-helpgit clone --depth 1 https://github.com/john-farina/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/commands/john-farina/claude-plugins/conjure-help)<a href="https://agentmods.dev/commands/john-farina/claude-plugins/conjure-help"><img src="https://agentmods.dev/badge/commands/john-farina/claude-plugins/conjure-help.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 | $0.00046 | $0.01672 |
| Opus 5 | $0.00023 | $0.00836 |
| Sonnet 5 | $0.00009 | $0.00334 |
| Haiku 4.5 | $0.00005 | $0.00167 |
Grade B, and why
conjure-help 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 3d 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.
**Storage:** script at `~/.claude/hooks/<name>.sh` + entry in `~/.claude/settings.json` How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conjure — Help
Conjure builds Claude Code extensions: skills (slash commands), agents (autonomous workers), hooks (event-driven scripts), and MCP servers (external connections). All commands support both create and update modes.
Which command do I use?
Does Claude need live access to an external system (DB, API, third-party service)?
YES → /conjure-mcp
Should it fire automatically on an event (file edit, tool call, session start)?
YES → /conjure-hook
Does Claude spawn it with its own context, model, or restricted tools?
YES → /conjure-agent
Does the user type a /command to trigger it?
YES → /conjure-skill
Not sure? → /conjure — auto-detects the type for you
Signal phrases:
| You say… | Use |
|---|---|
| "connect to", "integrate with", "query [DB/API]", "stop copy-pasting from [service]" | /conjure-mcp |
| "whenever", "every time", "fires when", "on save", "after tool call", "session start" | /conjure-hook |
| "investigate", "search in isolation", "spawn a worker", "orchestrate" | /conjure-agent |
| "command", "slash command", "workflow I trigger", "checklist" | /conjure-skill |
Command Reference
/conjure — Unified entry point
Auto-detects type, runs intake, delegates to the right command.
/conjure Ask what you want to build
/conjure <description> Auto-classify from description
/conjure help Show this help
/conjure-skill — Slash commands & workflows
/conjure-skill <name> Create (if new) or update (if exists)
/conjure-skill <name> faster Speed-optimize: add ! pre-injection, strip prose
/conjure-skill <name> simpler Reduce to 80% case, move edge cases to bottom
/conjure-skill <name> detailed Expand: add phases, edge cases, examples
/conjure-skill <name> blank Keep frontmatter, clear body
/conjure-skill <name> review Quality gate: report issues + fix them
/conjure-skill <description> Create with inline description — builds immediately
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.
- 3d ago First seen · 181 lines · 46 tokens per session scan B 70a21fdda1fc
conjure-help is a command published in the GitHub repository john-farina/claude-plugins (1 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 1,672 once invoked, about $0.0002 per session on Opus 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
sm-sail
Command "sm-sail" from ScienceIsNeato/slop-mop, covering /sm-sail — drive a pr to green, autonomously, the loop, when sail parks on review threads, when to stop before "pr ready" — only two reasons and expect convergence, not one pass.
sm-buff
You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…
sm-wake-angry-drunk-captain
The last-resort verb. Use it ONLY when the loop is genuinely exhausted: barnacles filed, gates green or truly unfixable, and the single remaining move is a human judgment call no sm verb can make for you.
sm-barnacle
Use when sm itself gives invalid guidance, blocks valid work, produces confusing output, or breaks install/upgrade/refit flow. Do not use this for real target-repo failures; fix those through the normal rail.
sm-init
Run when you find a repo with sm installed but no .sbconfig.json — or after upgrading slopmop to pick up new gates.
sm-refit
Run slop-mop's one-time onboarding remediation rail for this repository.