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.
git clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/god-mode)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/god-mode"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/god-mode/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/commands/sifxprime/kodelyth-ecc/god-mode"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/god-mode.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.00038 | $0.00883 |
| Opus 5.5 | $0.00015 | $0.00353 |
| Sonnet 5.5 | $0.00008 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
god-mode 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 1mo 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/god-mode — Build It Properly
Nine specialists in a six-stage pipeline. This is not /project-launch (which fires everyone at once) — GOD mode is sequential where sequence matters, parallel where it doesn't, and it refuses to call anything done that it hasn't proven.
The pipeline
| Stage | Agents | What happens |
|---|---|---|
| Recall | — | Search local memory for prior solutions to this problem |
| Design ∥ | architect + code-architect |
Blueprint: files, interfaces, data flow, build order |
| Build → | pair-programmer + tdd-guide |
Implement test-first; tests must actually run |
| Self-critique ∥ | type-design-analyzer + api-guardian + ux-reviewer |
Attack our own work before anyone else can |
| Harden ∥ | performance-optimizer + refactor-cleaner |
Hot spots and dead weight, no behaviour change |
| Prove | — | Run the verification commands |
∥ = parallel · → = sequential
Usage
/god-mode add rate limiting to the payments API
/god-mode harden the webhook signature verification
/god-mode # asks what to build
Preview the plan and cost from the terminal first:
kodelythecc god --task "add rate limiting to the payments API"
Instructions to the assistant
Run the stages in order. Do not skip Recall and do not skip Prove.
Stage 1 — Recall (do this first, always)
Search local memory for prior work on this problem:
- Use the
recall_memoryMCP tool, orkodelythecc memory recall "<task>". - For each relevant hit, state: the past problem, the approach that worked, and whether it applies here.
- If nothing relevant exists, say so plainly. Never invent a memory.
Stage 2 — Design (parallel)
Launch architect and code-architect together via the Task tool. Produce one concrete blueprint: exact files, interfaces, data flow, build order. No hand-waving.
Stage 3 — Build (sequential)
Launch pair-programmer and tdd-guide. Write the test first, watch it fail, implement, watch it pass. Report which files you created or changed.
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.
- 1mo ago First seen · 86 lines · 38 tokens per session scan A 03c9c13f7222
god-mode is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 20d ago), licensed MIT. It adds 38 tokens to every session and 883 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other commands, from other repositories
test
Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern.
hatch3r-bug-pipeline
Run a known-cause bug fix through a 3-phase test-first pipeline -- reproduce + root-cause, regression-test + fix together, then root-cause-depth review -- with full sub-agent delegation.
test
A test-driven development workflow, or TDD, where tests describing the expected behavior are written before the implementation. For bugs, it first adds a test that reproduces the failure.
build-tdd
SAM Build-TDD Workflow - Implements a single user story using RED-GREEN-REFACTOR with conditional UI/CSS/A11y/Security review.
plan-n-build
SAM end-to-end composer - runs plan, then tdd for every story, then comprehensive docs. The one-shot PRD-to-working-code experience.
kotlin-test
Enforce TDD workflow for Kotlin. Write Kotest tests first, then implement. Verify 80%+ coverage with Kover.