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.
/plugin marketplace add SyloRei/claude-godmode/plugin install 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/skills/sylorei/claude-godmode/brief)<a href="https://agentmods.dev/skills/sylorei/claude-godmode/brief"><img src="https://agentmods.dev/badge/skills/sylorei/claude-godmode/brief/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sylorei/claude-godmode/brief"><img src="https://agentmods.dev/badge/skills/sylorei/claude-godmode/brief.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.03564 |
| Opus 5 | $0.00023 | $0.01782 |
| Sonnet 5 | $0.00009 | $0.00713 |
| Haiku 4.5 | $0.00005 | $0.00356 |
Grade A, and why
brief 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 9d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brief
Capture everything implementation needs for roadmap unit $N in one artifact: why it matters (problem/goal), what is in and out of scope, and a spec of verifiable acceptance criteria. A good brief leaves no room for "I assumed you meant…".
Run after /mission has produced a numbered roadmap. The brief is the contract /plan N and /build N read from. This is the second step of the spine: /mission → /brief N → /plan N → /build N → /verify N → /ship.
The artifact lives in the consumer's repo, never in the plugin source, scoped to the active mission:
.planning/missions/<mission_id>/briefs/NN-name/BRIEF.md— the single brief for roadmap unit$N.
<mission_id> is the active mission's NN-slug, resolved from workflow state ("$gm/godmode-state" get mission_id; see the helper-resolution note in Process), so /brief always operates on whatever mission is currently active. .planning/PROJECT.md and .planning/STATE.md stay at the .planning/ root (project-global).
One brief artifact per unit. No second file at this step — /plan N adds PLAN.md later. Write BRIEF.md and nothing else.
Auto Mode
Auto Mode suppresses confirmation prompts, not the clarifying questions that decide what gets built. The brief is where this unit's quality is set — a spec built on silent guesses sends /plan and /build confidently in the wrong direction. So in either mode:
- Ask the consequential questions — the ones whose answer materially changes the spec (scope edges, the exact bar for "done", behavioral choices that genuinely diverge, hard constraints) AND that the roadmap entry /
.planning/PROJECT.md/ README / repo cannot answer. Auto Mode does not waive these; it just batches them. - Assume the trivial — for low-stakes gaps the context reasonably implies, pick a sensible default and record it under an Assumptions heading instead of asking.
- Never ask what the repo already answers. Treat user course-corrections as normal input.
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.
- 9d ago First seen · 249 lines · 46 tokens per session scan A 2dbf0cc9ecf4
brief is a skill published in the GitHub repository SyloRei/claude-godmode (3 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 3,564 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.
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.
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.
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.
figma-extract
Exhaustive Figma node extraction: download every detail down to leaf nodes and cache everything locally. Call Figma once, never twice. Use before any pixel-perfect implementation. Prioritizes complete local dumps over repeated API calls.