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 skills add SyloRei/claude-godmode --skill skillgit 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.
![agentmods badge for [object Object]](/badge/skills/sylorei/claude-godmode/skill.svg?v=0-8-A){kind=icon}
[](https://agentmods.dev/skills/sylorei/claude-godmode/skill)<a href="https://agentmods.dev/skills/sylorei/claude-godmode/skill"><img src="https://agentmods.dev/badge/skills/sylorei/claude-godmode/skill.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.00008 | $0.00057 |
| Opus 5 | $0.00004 | $0.00028 |
| Sonnet 5 | $0.00002 | $0.00011 |
| Haiku 4.5 | $0.00001 | $0.00006 |
Grade A, and why
[object Object] 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 7d 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.
What it actually says
{{name}}
{{description}}
Related
- [List sibling skills, commands, or agents this skill hands off to or builds on.]
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 18 lines · 8 tokens per session scan A e7681a2bde27
[object Object] is a skill published in the GitHub repository SyloRei/claude-godmode (3 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 57 once invoked, about $0.0000 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 skills, from other repositories
figma-verification
Extract Figma design specs before implementing UI components. Use depth 5, cache to disk, extract ALL properties, map to design system tokens.
interaction-design
Use when designing how a UI feels to use. Covers audience dimensions, discoverability, mode communication, keyboard-first UX, feedback timing, empty states, and information density. Includes WCAG 2.1 AA compliance audit. Companion to visual-design.
browser-testing
Adversarial browser testing. Use when testing UI behavior, verifying network requests, checking console errors, filling forms, or handling dialogs. The goal is finding bugs, not confirming happy paths.
debugging-protocol
Systematic protocol for diagnosing broken behavior and making recurrence structurally impossible. Schema mismatch causes 80% of bugs. Use when something isn't showing, isn't working, or is still broken after a fix attempt.
plan-mode
CEO and engineering review after spec-writing. Auto-selects weight class from the spec format (skip for task-mode, eng-only for routine, full CEO+eng for high-risk). Run /spec-writing first.
pr-review
Use when reviewing a PR or responding to review comments on your own PR. Detects authorship automatically and runs the correct mode. Never makes code changes when reviewing someone else's work.