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/conjuregit 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)<a href="https://agentmods.dev/commands/john-farina/claude-plugins/conjure"><img src="https://agentmods.dev/badge/commands/john-farina/claude-plugins/conjure.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.00062 | $0.02578 |
| Opus 5 | $0.00031 | $0.01289 |
| Sonnet 5 | $0.00012 | $0.00516 |
| Haiku 4.5 | $0.00006 | $0.00258 |
Grade B, and why
conjure 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.
cat ~/.claude/conjure-config.md 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 0: Help Check
If $ARGUMENTS is "help" or "--help" or "-h": tell the user to run /conjure-help for the full reference, then stop.
Phase 0.5: Load User Preferences
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 ## global and any type-specific sections throughout 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: Classify + Initial Intake
The user wants to build something. They may or may not know what type.
Their request: $ARGUMENTS
Run the classification + intent batch. Use AskUserQuestion with these questions (skip any that $ARGUMENTS already answers clearly):
Q1 "Access" — "Does this need to connect Claude to an external system it can't reach natively (a database, REST API, third-party service like Jira/Linear/Notion)?" Options:
- Yes — Claude needs live access to something external
- No — it works with what Claude already has access to
- Not sure
Q2 "Trigger" — "How does this get activated?" (skip if Q1 = Yes) Options:
- I type a
/commandin the prompt - Automatically when something happens (file edit, tool call, session start, stop)
- Claude spawns it programmatically with its own context and tools
- Not sure — I just know what I want it to do
Q3 "Job" — "What is the ONE thing this does? Be specific — not 'helps with X' but 'does Y when Z happens.'" Options:
- Connects Claude to an external system / API / database
- Runs a multi-step workflow I trigger manually
- Fires automatically and blocks, logs, or injects context
- Executes a focused research or analysis task in isolation
Q4 "Scope" — "Should this work in all projects or just this one?" Options:
- All projects (user-global)
- This project only
- Not sure
Phase 2: Classify
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 · 237 lines · 62 tokens per session scan B 11e5116f9d07
conjure is a command published in the GitHub repository john-farina/claude-plugins (1 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 2,578 once invoked, about $0.0003 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
docs-update
You are executing the /dogma:docs-update command. Your task is to synchronize documentation across README files and wiki articles, ensuring everything is up-to-date.
sanitize-git
You are executing the /dogma:sanitize-git command. Your task is to find and remove AI/Claude traces from git history and fix tracking issues where files that should be excluded are still being tracked.
session-init
You are the Main Agent in an orchestrated workflow. Read and internalize these working instructions.
permissions
Create or update DOGMA-PERMISSIONS.md to configure what Claude can do autonomously.
project
Command "project" from Marcel-Bich/marcel-bich-claude-marketplace, covering credo project target, with an argument (set the pin) and without an argument (show the current target).
sandbox-promote
Promote an accepted, version-worthy WIP artifact from .credo/sandbox-tmp/ / to .credo/sandbox/ /. is the sandbox-tmp folder name (argument: $1).