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 skills/arbazkhan971/godmode/agentnpx skills add arbazkhan971/godmode --skill agentgit 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/skills/arbazkhan971/godmode/agent)<a href="https://agentmods.dev/skills/arbazkhan971/godmode/agent"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/agent.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.00043 | $0.02845 |
| Opus 5 | $0.00022 | $0.01422 |
| Sonnet 5 | $0.00009 | $0.00569 |
| Haiku 4.5 | $0.00004 | $0.00284 |
Grade A, and why
agent 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent — AI Agent Development
Activate When
- User invokes
/godmode:agent - User says "build an AI agent", "create an agent", "add tools to my agent"
- User says "design agent memory", "agent keeps looping", "agent safety"
- When building autonomous or semi-autonomous LLM-powered systems
- When
/godmode:promptidentifies a need for agentic capabilities (tool use, multi-step reasoning) - When
/godmode:ragneeds to be wrapped in an agent loop - When the orchestrator detects agent frameworks (LangChain, LlamaIndex, CrewAI, AutoGen, custom agent loops) in code
Workflow
Step 1: Agent Discovery & Requirements
Understand what the agent must accomplish:
AGENT DISCOVERY:
Purpose: <what the agent must autonomously accomplish>
Type:
- Single-agent: One agent with tools (most common)
- Multi-agent: Multiple specialized agents coordinating
- Human-in-the-loop: Agent proposes, human approves critical actions
User interaction:
- Conversational: User chats with agent in real-time
- Autonomous: Agent runs a task to completion without user input
- Supervised: Agent asks for confirmation at decision points
Environment:
- Tools available: <list of APIs, databases, code execution, file systems>
- External systems: <services the agent will interact with>
If the user hasn't specified, ask: "What should this agent do autonomously? What tools does it need?"
Step 2: Architecture Pattern Selection
Select the agent architecture pattern:
AGENT ARCHITECTURE SELECTION:
Patterns:
| Pattern | Best for |
|--|--|
| ReAct | General-purpose tool use, step-by-step reasoning |
| (Reason + Act) | with tool calls. Simple, effective, well-understood. |
| Plan-and-Execute | Complex tasks needing upfront planning. Planner |
| | creates step list, executor follows it. Good for |
| | multi-step tasks with clear decomposition. |
| Reflexion | Tasks requiring self-correction. Agent attempts, |
| | evaluates own output, and retries with feedback. |
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 · 296 lines · 43 tokens per session scan A 919f67344c2c
agent is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 7d ago), licensed MIT. It adds 43 tokens to every session and 2,845 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-30.
Other skills, from other repositories
jobs-to-be-done
Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also…
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
codex
Run benchmark-selected GPT-5.6 work through the Codex CLI.
scienceworld-growth-focuser
Use when you have planted a seed or need to track a plant's growth stage (sprouting, flowering, reproduction). Applies the 'focus on' action to a specific plant or biological entity to signal intent and monitor its development. Trigger after planting or when you need to observe life cycle progression in the…
iterate-pivot-decision
Documents a strategic pivot or persevere decision with the evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.
ralph-specum-requirements
This skill should be used only when the user explicitly asks to use $ralph-specum-requirements, or explicitly asks Ralph Specum in Codex to run the requirements phase.