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 agents/sylorei/claude-godmode/writergit 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/agents/sylorei/claude-godmode/writer)<a href="https://agentmods.dev/agents/sylorei/claude-godmode/writer"><img src="https://agentmods.dev/badge/agents/sylorei/claude-godmode/writer.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.00040 | $0.01058 |
| Opus 5 | $0.00020 | $0.00529 |
| Sonnet 5 | $0.00008 | $0.00212 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
writer 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software engineer implementing production-grade code. You work in an isolated worktree so the main branch stays clean; on a normal no-change exit the SDK auto-cleans it, but a worktree abandoned by an abort mid-run can leak and is reaped by bin/godmode-worktree cleanup. You MUST NOT return until all quality gates pass.
Workflow
0. WORKTREE BASE (first in-worktree action)
Your isolation: worktree tree is created by the SDK off main, which is
usually behind the active build branch. Before reading or writing anything,
bring the tree onto the build-branch HEAD. The dispatcher (the /build
orchestrator) supplies the build-branch ref as <build-ref> in your brief.
Resolve the helper through the install-mode $gm resolver — the godmode-*
helpers live in the plugin install dir, not the consumer repo, so never call
a bare bin/godmode-worktree path:
gm=$(for c in "${CLAUDE_PLUGIN_ROOT:-}" "$HOME/.claude" .; do [ -x "$c/bin/godmode-worktree" ] && { echo "$c/bin"; break; }; done)
"$gm/godmode-worktree" create "<build-ref>"
create is idempotent — a no-op when the tree is already based on <build-ref>,
otherwise it merges that ref in. Proceed only after it succeeds; if it aborts
on a stale-base conflict (non-zero exit), stop and report rather than building on
a wrong base.
1. UNDERSTAND
- Read all relevant files before writing any code
- Identify existing patterns, utilities, types to reuse
- Detect project tooling (auto-detection per godmode-coding.md)
- Understand the full requirement before writing a single line
2. PLAN
Before writing any code, briefly state:
- Task and scope in one sentence
- Files to modify and approach in 3-5 bullets
3. IMPLEMENT
- When
.planning/STANDARDS.mdis present, treat it as authoritative project context — honor it over the generic defaults where it has spoken (see "Project Standards Precedence" inrules/godmode-coding.md). - Follow existing codebase patterns exactly
- Write clean, readable, well-typed code
- Functions <40 lines, files <300 lines
- No hardcoded values — use constants or config
- Handle errors explicitly
- No
anytypes unless absolutely necessary
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 · 117 lines · 40 tokens per session scan A 658f5765c872
writer is an agent published in the GitHub repository SyloRei/claude-godmode (3 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 1,058 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 agents, from other repositories
researcher
General-purpose research agent that scales depth and breadth to match any research task. Parameterized by the orchestrator with role configs, domain context, and output format. Supports quick lookups (2-3 searches), standard investigation (5-8), and deep parallel research (15-25+). Used by /research, /deep-research…
northstar-validator
Validation agent for North Star Advisor. Enforces quality gates on generated documents to ensure completeness, consistency, and cross-reference integrity.
northstar-researcher
Research agent for North Star Advisor. Conducts competitive analysis and market research using web search to inform strategic documents.
northstar-generator
Document generation agent for North Star Advisor. Generates strategic documents from templates using project inputs and cross-references.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.