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/cubetribe/claudecode_godmode-on/workflow-designgit clone --depth 1 https://github.com/cubetribe/ClaudeCode_GodMode-OnWrote 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/cubetribe/claudecode_godmode-on/workflow-design)<a href="https://agentmods.dev/agents/cubetribe/claudecode_godmode-on/workflow-design"><img src="https://agentmods.dev/badge/agents/cubetribe/claudecode_godmode-on/workflow-design.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 | $0.00041 | $0.00867 |
| Opus 5 | $0.00020 | $0.00434 |
| Sonnet 5 | $0.00008 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
workflow-design 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 116 lines · 41 tokens per session scan A 8189ec302763
workflow-design is an agent published in the GitHub repository cubetribe/ClaudeCode_GodMode-On (47 stars, last pushed yesterday), with no licence file. It adds 41 tokens to every session and 867 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-30.
Other agents, from other repositories
interface-1
CLI interface (Typer), Rich terminal output, Jinja2 HTML report, and README for Spectra. The user-facing layer.
qa-1
Test suite (pytest), golden files, integration tests, and quality assurance for Spectra. Ensures everything works correctly.
reviewer
Dispatched by tri-review, mega-pr, and pr-ready workflows to perform an independent code review or to classify unresolved PR review comments into codefix, stylenit, question, falsepositive, or outofscope. Read-only; returns findings and classifications.
security-auditor
Dispatched by tri-security, audit, and pr-ready workflows to audit code for vulnerabilities across injection, auth, secrets management, dependencies, and unsafe patterns. Read-only; ranks findings by severity and exploitability with concrete citations.
test-writer
Dispatched by the test-gen workflow to generate tests for a target file or module, then iterate on failing tests until they pass. Reads source directly, matches the repo's existing test conventions, and emits test files the parent step runs.
documenter
Dispatched by the doc-gen workflow to generate reference documentation for a specified target (module, package, file). Reads source directly, matches existing doc style, and emits an overview + API reference + usage examples + configuration notes.