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 instructions/sylorei/claude-godmode/agents-mdgit clone --depth 1 https://github.com/SyloRei/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/instructions/sylorei/claude-godmode/agents-md)<a href="https://agentmods.dev/instructions/sylorei/claude-godmode/agents-md"><img src="https://agentmods.dev/badge/instructions/sylorei/claude-godmode/agents-md.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.07502 | $0.07502 |
| Opus 5 | $0.03751 | $0.03751 |
| Sonnet 5 | $0.01500 | $0.01500 |
| Haiku 4.5 | $0.00750 | $0.00750 |
Grade A, and why
claude-godmode AGENTS.md 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 5d 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 — 703 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file is the cross-tool export of the claude-godmode agent roster and
engineering rules. It is generated by bin/godmode-agents and is meant to be
read standalone by any AI coding harness (Codex, Cursor, OpenCode, and others)
that does not have the claude-godmode plugin installed.
The claude-godmode workflow spine is:
/godmode → /mission → /brief → /plan → /build → /verify → /ship
Each stage hands off to the next: /godmode orients, /mission frames the
goal, /brief specifies what and why, /plan decomposes into steps, /build
implements one step at a time behind quality gates, /verify checks the brief's
acceptance criteria, and /ship lands the change. The agents below are the
specialists this spine delegates to; the rules below are the engineering
standards every agent and stage upholds.
This document is generated — do not edit it by hand. Run bin/godmode-agents
to regenerate it from agents/*.md and rules/godmode-*.md.
Agent roster
These are the specialist agents the workflow spine delegates to.
architect
System design and architecture agent. Use for: designing new systems, evaluating tradeoffs, planning migrations, reviewing architecture, API design, database schema design. Advisory only — does not modify code.
code-reviewer
Code-level reviewer. Use for: checking whether a change does the thing RIGHT — bugs, edge cases, security, performance, readability, and pattern violations in the implementation. Catches 'thing wrong' errors. Read-only.
convention-reviewer
Convention review lens. Use for: checking naming, file structure, and adherence to the project's existing conventions and patterns in a change. Read-only — analyzes and reports, cannot modify code.
debugger
Root-cause debugging agent that finds and fixes bugs in an isolated worktree. Use for: diagnosing failures, tracking down root causes, fixing regressions. Returns a branch with a minimal, tested fix and all quality gates green.
doc-writer
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.
- 5d ago First seen · 703 lines · 7,502 tokens per session scan A 0575e79f5ba6
claude-godmode AGENTS.md is an instructions file published in the GitHub repository SyloRei/claude-godmode (3 stars, last pushed 2mo ago), licensed MIT. It adds 7,502 tokens to every session, about $0.0375 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 instructions, from other repositories
skill-engine CLAUDE.md
Claude Code instructions for nick-railsback/skill-engine, covering skill-engine — standing rules, before proposing a commit, versions and git.
erpaval CLAUDE.md
Instructions for theagenticguy/erpaval, covering erpaval-plugin, repo structure, version management, tools and hooks.
n8n-skills CLAUDE.md
Claude Code instructions for PentagonRBX/n8n-skills, covering claude.md, 專案概述, 常用開發指令, 核心架構 and 1. collectors（收集器）- src/collectors/.
tripod CLAUDE.md
Claude Code instructions for joryeugene/tripod, covering priority 0: the tripod, 1. antifragile, 2. simple (hickey: complecting), 3. research first (stand on giants) and priority 1: the contract.
ship-it open-pr.instructions.md
Instructions for khrichtchatyi/ship-it: When the user asks to open, create, or submit a pull request, follow the skill in skills/open-pr/SKILL.md in full: verify gh is authenticated, resolve the target repository and default branch, push the current branch, open one pull request with a title and body derived from the…
agent-skills CLAUDE.md
Instructions for mindbox-cloud/agent-skills, covering agent-skills — developer guide for claude code, repository purpose, repository structure, how to add a new plugin and step 1 — create the directory structure.