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/arbazkhan971/godmode/gemini-mdgit clone --depth 1 https://github.com/arbazkhan971/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/arbazkhan971/godmode/gemini-md)<a href="https://agentmods.dev/instructions/arbazkhan971/godmode/gemini-md"><img src="https://agentmods.dev/badge/instructions/arbazkhan971/godmode/gemini-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.02466 | $0.02466 |
| Opus 5 | $0.01233 | $0.01233 |
| Sonnet 5 | $0.00493 | $0.00493 |
| Haiku 4.5 | $0.00247 | $0.00247 |
Grade A, and why
godmode GEMINI.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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Godmode for Gemini CLI
@./skills/godmode/SKILL.md @./skills/principles/SKILL.md
Verify Installation
After running the install script, confirm everything is set up correctly:
bash adapters/gemini/verify.sh
This checks that Gemini CLI can find the Godmode configuration, skill files, and agent definitions. If any check fails, the script reports what is missing and how to fix it.
Tool Mapping
Gemini CLI tools map to Godmode skill references as follows:
| Skill Reference | Gemini Tool |
|---|---|
| Read | read_file |
| Write | write_file |
| Edit | replace |
| Bash | run_shell_command |
| Grep | grep_search |
| Glob | glob |
| TodoWrite | write_todos |
| Skill | activate_skill |
When a skill says "use Read to examine the file," use read_file. When it says "use Bash to run tests," use run_shell_command. Apply this mapping throughout.
How to Use Skills
Godmode has 135 skills and 7 subagents. The orchestrator (/godmode) auto-detects which to invoke. Users can also invoke directly: /godmode:skillname.
When a user invokes a skill (e.g., /godmode:secure), read the full skill file before executing:
read_file("./skills/secure/SKILL.md")
Then follow that skill's workflow exactly.
General pattern:
read_file("./skills/<skill-name>/SKILL.md")
Subagents (7 Built-in)
Godmode ships with 7 specialized agents. For complex tasks, use the planner to decompose, then dispatch builders in parallel.
| Agent | Role | Read agents/*.md for full instructions |
|---|---|---|
| planner | Decomposes goals → parallel tasks mapped to skills | read_file("./agents/planner.md") |
| builder | Implements a task following a skill workflow | read_file("./agents/builder.md") |
| reviewer | Reviews code for correctness + security | read_file("./agents/reviewer.md") |
| optimizer | Autonomous measure → modify → verify loop | read_file("./agents/optimizer.md") |
| explorer | Read-only codebase recon | read_file("./agents/explorer.md") |
| security | STRIDE + OWASP audit | read_file("./agents/security.md") |
| tester | TDD test generation | read_file("./agents/tester.md") |
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 · 233 lines · 2,466 tokens per session scan A 53852ba0c525
godmode GEMINI.md is an instructions file published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 8d ago), licensed MIT. It adds 2,466 tokens to every session, about $0.0123 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-30.
Other instructions, from other repositories
agents CLAUDE.md
Claude Code instructions for navox-labs/agents, covering claude.md — navox-labs/agents, what this repo is, non-negotiable rules, commands and project memory.
river-review GEMINI.md
Gemini CLI instructions for s977043/river-review, covering gemini instructions (river-review), 必須チェック, gemini-specific tips, prompt assembly and development tips.
piratebao copilot-instructions.md
Instructions for d4551/piratebao: PirateBao kraken active by default. Respond like pirate captain packing dumpling cargo: dense, exact, no wasted wrap.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.