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 commands/sylorei/claude-godmode/adrgit 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/commands/sylorei/claude-godmode/adr)<a href="https://agentmods.dev/commands/sylorei/claude-godmode/adr"><img src="https://agentmods.dev/badge/commands/sylorei/claude-godmode/adr.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.00033 | $0.00818 |
| Opus 5 | $0.00016 | $0.00409 |
| Sonnet 5 | $0.00007 | $0.00164 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
adr 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/adr — write an Architecture Decision Record
A focused, single-shot generator. Capture one architectural decision as a well-formed ADR. This is a reactive helper — it does not spawn agents and is not part of the spine.
The Job
- Identify the decision being recorded.
- Read the surrounding change/context.
- Produce a complete ADR with all four sections.
1. Gather context
Read whatever explains the decision — the relevant diff, the files it touches, and any motivating discussion in the request:
git diff --stat # what changed
git log --oneline -10 # recent direction
Ask the user only what you cannot infer (e.g. alternatives considered, the
driving constraint) — and when you ask, follow the shared recommendation
convention (godmode:recommend-convention) in rules/godmode-recommend.md: its
clarifying rendering leads with your best-inferred answer to override, not a
blank prompt. So state what you'd record and invite correction:
I'll record the alternatives as in-process queue vs. Redis from the diff — tell me if I missed one.
(Not: "what alternatives did you consider?")
2. Produce the ADR
Emit a single Markdown document with these exact sections, in order:
# NNNN. <short title in imperative mood>
## Status
Proposed | Accepted | Superseded by ADR-MMMM (pick one)
## Context
The forces at play: the problem, the constraints, the requirement that makes a
decision necessary. State facts, not the choice.
## Decision
The change being made, in active voice ("We will …"). One decision per record.
## Consequences
What becomes easier and what becomes harder as a result — both the positive and
the negative. Note follow-on work and any new constraints introduced.
3. Suggest a home
Suggest (do not require) a path like docs/adr/NNNN-title.md, numbering one
above the highest existing ADR. Writing the file is a consequential step, so
pause with the convention's confirm/proceed rendering — lead with a Recommended:
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 · 103 lines · 33 tokens per session scan A df6f5e9cb420
adr is a command published in the GitHub repository SyloRei/claude-godmode (3 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 818 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 commands, from other repositories
release
Guided release for the skill-engine repo. Bumps the six version surfaces, drafts the CHANGELOG entry, runs validators, then pauses for the maintainer to commit, push, and tag manually. Accepts major / minor / patch / explicit X.Y.Z.
advisor-build
Research and generate strategic documents. Runs domain research, then generates documents informed by findings.
advisor
Begin strategic discovery through open exploration. Acts as your thinking partner to articulate what you're building.
resume
Resume generation from the last checkpoint after interruption.
export
Package docs and ai-context.yml into a shareable zip file.
help
Display available commands and usage information.