godmode

godmode is a command for Claude Code from SyloRei/claude-godmode. It costs 34 tokens per session (1,737 once invoked), scanned A, original, MIT.

A command that gives a short status summary of the current God-Mode workflow and the next command to run. It checks the available skills and agents along with recorded workflow state.

In plain words
What is it for?
Use it when you need orientation in a God-Mode project, including what is complete and the exact next action.
Why use it?
It helps you quickly understand where work stands without reading the whole project or remembering previous steps. The result is limited to five lines.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the claude-godmode plugin — 14 skills, 4 commands, 19 agents, 7 hooks, 3 MCP servers shipped together

Good fit Use it when you need orientation in a God-Mode project, including what…

Compare 6 commands from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add SyloRei/claude-godmode
Claude Code
/plugin install claude-godmode

Made for: Claude Code.

Or install claude-godmode, the plugin that ships this one along with the rest of its 14 skills, 4 commands, 19 agents, 7 hooks, 3 MCP servers.

Wrote 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.

agentmods badge for godmode

README.md
[![agentmods](https://agentmods.dev/badge/commands/sylorei/claude-godmode/godmode.svg)](https://agentmods.dev/commands/sylorei/claude-godmode/godmode)
Your own site
<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>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,737 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 6d ago against content hash 930f588906ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

commands/godmode.md · 127 lines

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

Read the full file on GitHub · 127 lines

Changes

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.

  1. 6d ago First seen · 127 lines · 34 tokens per session scan A 930f588906ef

Subscribe to this mod's changes

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.