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 SyloRei/claude-godmode/plugin install claude-godmodeWrote 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/sylorei/claude-godmode/godmode)<a href="https://agentmods.dev/commands/sylorei/claude-godmode/godmode"><img src="https://agentmods.dev/badge/commands/sylorei/claude-godmode/godmode.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.00034 | $0.01737 |
| Opus 5 | $0.00017 | $0.00869 |
| Sonnet 5 | $0.00007 | $0.00347 |
| Haiku 4.5 | $0.00003 | $0.00174 |
Grade A, and why
godmode scanned grade A with 0 findings 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 6d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/godmode — orient
Answer one question in 5 lines or fewer: where am I, what's done, and what is the single next command to run? Derive everything below from the live filesystem and the recorded workflow state — never from a memorized list.
1. Resolve paths (plugin / manual / repo modes)
The same logic runs whether God-Mode is installed as a plugin, installed manually into ~/.claude/, or run from a repo checkout. Resolve the plugin root, then the manifest:
# Plugin mode sets CLAUDE_PLUGIN_ROOT. Manual install lives under ~/.claude.
# Repo checkout: the command file's own tree. Pick the first that has plugin.json.
ROOT=""
for cand in "${CLAUDE_PLUGIN_ROOT:-}" "$HOME/.claude" "$(pwd)"; do
[ -n "$cand" ] || continue
if [ -f "$cand/.claude-plugin/plugin.json" ] || [ -d "$cand/agents" ]; then
ROOT="$cand"
break
fi
done
[ -n "$ROOT" ] && echo "root: $ROOT" || echo "root: (unresolved — using repo-relative fallbacks)"
If ROOT stays empty, fall back to the repo-relative dirs agents/, skills/, commands/ and .claude-plugin/plugin.json from the current working directory.
2. Read the canonical version
.claude-plugin/plugin.json:.version is the single source of truth — read it at runtime, never hardcode:
MANIFEST="$ROOT/.claude-plugin/plugin.json"
[ -f "$MANIFEST" ] || MANIFEST=".claude-plugin/plugin.json"
VERSION=$(jq -r '.version // "unknown"' "$MANIFEST" 2>/dev/null || echo "unknown")
echo "version: $VERSION"
3. Read the workflow state
/mission records the workflow keys via bin/godmode-state — including the active mission (mission_id + human-readable mission_name). Read them to derive the next action. Resolve the helper from the plugin root, then ~/.claude, then the repo:
STATE_BIN=""
for cand in "$ROOT/bin/godmode-state" "$HOME/.claude/bin/godmode-state" "bin/godmode-state"; do
if [ -x "$cand" ]; then STATE_BIN="$cand"; break; fi
done
if [ -n "$STATE_BIN" ] && [ -f .planning/STATE.md ]; then
MISSION_ID=$("$STATE_BIN" get mission_id)
MISSION_NAME=$("$STATE_BIN" get mission_name)
ACTIVE=$("$STATE_BIN" get active_unit)
STATUS=$("$STATE_BIN" get status)
NEXT=$("$STATE_BIN" get next_command)
echo "mission_id: $MISSION_ID"
echo "mission_name: $MISSION_NAME"
echo "active_unit: $ACTIVE"
echo "status: $STATUS"
echo "next_command: $NEXT"
else
echo "cold_start: true" # no .planning/STATE.md yet
fi
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.
- 6d ago First seen · 127 lines · 34 tokens per session scan A 930f588906ef
godmode is a command published in the GitHub repository SyloRei/claude-godmode (3 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 1,737 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
recall-save
Generate / overwrite .recall/context.md with Recall's local offline summarizer.
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…
ccc-orchestrate
Sequential and tmux/worktree orchestration guidance for multi-agent workflows.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
design
A command that turns an existing plan into a detailed technical design for building the feature.
complete
Signal that a skill's work is complete. Triggers downstream subscriptions with "when": "complete" timing. Automatically invoked — do not run manually.