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-agentgit 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-agent)<a href="https://agentmods.dev/commands/john-farina/claude-plugins/conjure-agent"><img src="https://agentmods.dev/badge/commands/john-farina/claude-plugins/conjure-agent.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.00027 | $0.04221 |
| Opus 5 | $0.00014 | $0.02110 |
| Sonnet 5 | $0.00005 | $0.00844 |
| Haiku 4.5 | $0.00003 | $0.00422 |
Grade B, and why
conjure-agent 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 4d 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 — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craft Agent
Creates or updates a Claude Code agent definition (~/.claude/agents/<name>.md or project-local).
Phase 0 — "Should this be an agent at all?"
Before creating anything, apply this gate. An agent is the RIGHT tool only when one of these is true:
- Context pollution — prior subtask results (1000+ tokens) would degrade reasoning on the next step
- True parallelism — independent workstreams that gain nothing from sharing a context window
- Tool overload — the job needs 15+ tools, or fundamentally conflicting behavioral modes (e.g., "never edit" and "always edit")
- Sustained specialization — the agent accumulates domain context across many calls that a generalist can't maintain
If none apply: a well-prompted single Claude call (or a skill/command) achieves equivalent results at 10-15x lower token cost. Say so and stop.
Redirect table — say this and stop if matched:
| Request sounds like… | Actually is… | Say… |
|---|---|---|
| "agent to commit my changes" | Skill — user-triggered, inline workflow | "This is better as a skill — run /conjure-skill <name>" |
| "agent to run lint whenever I save" | Hook — fires automatically | "This is better as a hook — run /conjure-hook <description>" |
| "agent to explain architecture" | Skill (reference) | "This is better as a skill — run /conjure-skill <name>" |
| "agent to search the codebase" | Agent ✅ — isolated context, specific tools | Continue |
| "agent to investigate crashes" | Agent ✅ — spawned programmatically | Continue |
| "agent to always do X" | Hook — automatic, event-driven | "This is better as a hook — run /conjure-hook <description>" |
If updating an existing agent: skip to Phase 1 — the decision was already made.
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 ## agents 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.
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.
- 4d ago First seen · 399 lines · 27 tokens per session scan B ffe4636cdb37
conjure-agent is a command published in the GitHub repository john-farina/claude-plugins (1 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 4,221 once invoked, about $0.0001 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.