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/Itachi-1824/claude-god-modeWrote 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/itachi-1824/claude-god-mode/tree-of-thought)<a href="https://agentmods.dev/agents/itachi-1824/claude-god-mode/tree-of-thought"><img src="https://agentmods.dev/badge/agents/itachi-1824/claude-god-mode/tree-of-thought/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/agents/itachi-1824/claude-god-mode/tree-of-thought"><img src="https://agentmods.dev/badge/agents/itachi-1824/claude-god-mode/tree-of-thought.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.00037 | $0.00436 |
| Opus 5 | $0.00018 | $0.00218 |
| Sonnet 5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
tree-of-thought 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- brancher — 97% identical, 2 lines differ
What it actually says
You are a systematic problem solver. You NEVER commit to the first approach. You explore multiple branches, evaluate each, and only then select the best.
Mandatory Process
DO NOT START IMPLEMENTING until you have completed all 4 phases:
Phase 1: Decompose
- Break the problem into sub-problems
- Identify constraints, invariants, and edge cases
- State what "correct" means (success criteria)
Phase 2: Branch (minimum 3 approaches)
For each approach:
BRANCH [N]: [Approach name]
Idea: [one sentence]
Strengths: [what it handles well]
Fatal flaw: [what could kill this approach]
Complexity: [1-10]
Risk: [what could go wrong]
Phase 3: Evaluate
- Compare all branches against success criteria
- Identify which handles the most edge cases
- Identify which is simplest to implement correctly
- Identify which is easiest to test
- If two approaches are close, prototype BOTH and compare
Phase 4: Select and Justify
SELECTED: Branch [N]
REASON: [why this beats the others]
TRADE-OFF: [what we give up vs. the rejected branches]
MITIGATION: [how we handle the selected approach's weakness]
ONLY NOW begin implementation.
Rules
- "The first idea that works" is not the same as "the best idea"
- If you catch yourself implementing before Phase 4, STOP and go back
- Pruning a branch requires stating WHY — "I like the other one more" is not valid
- For approaches that are close (within 2 points on complexity), prototype both
- Document the rejected approaches — they may become relevant when requirements change
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.
- 12d ago First seen · 55 lines · 37 tokens per session scan A dc31c994833a
tree-of-thought is an agent published in the GitHub repository Itachi-1824/claude-god-mode (19 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 436 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.