A structured analysis command for difficult problems and decisions. It gathers evidence, considers several viewpoints, tests the reasoning against objections, and produces a conclusion; its instructions require responses in Chinese.

Use it to clarify an ambiguous problem, collect evidence about technology or best practices, compare perspectives, stress-test proposed conclusions, and synthesise a recommendation.

It helps expose weak assumptions and risks that a quick answer may miss. The staged process makes complex reasoning easier to follow and review with a person.

ultra-think — Command for Claude Code by rocky2431/ultra-builder-pro

Install

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.

Clone the repo

git clone --depth 1 https://github.com/rocky2431/ultra-builder-pro

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/rocky2431/ultra-builder-pro/ultra-think/github.svg)](https://agentmods.dev/commands/rocky2431/ultra-builder-pro/ultra-think)

Your own site

<a href="https://agentmods.dev/commands/rocky2431/ultra-builder-pro/ultra-think"><img src="https://agentmods.dev/badge/commands/rocky2431/ultra-builder-pro/ultra-think/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/rocky2431/ultra-builder-pro/ultra-think"><img src="https://agentmods.dev/badge/commands/rocky2431/ultra-builder-pro/ultra-think.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 909 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00012	$0.00909
Opus 5.5	$0.00005	$0.00364
Sonnet 5.5	$0.00002	$0.00182
Haiku 4.5	$0.00001	$0.00091

Measured 2mo ago against content hash da16b2ed8f86, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ultra-think 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 2mo 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.

commands/ultra-think.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/ultra-think

Workflow Tracking (MANDATORY)

On command start, create tasks for each major step using TaskCreate:

Step	Subject	activeForm
1	Scope Check	Clarifying problem...
2	Evidence Gathering	Gathering evidence...
3	Multi-Perspective Analysis	Analyzing perspectives...
4	Adversarial Stress-Testing	Stress-testing reasoning...
5	Synthesis	Synthesizing recommendation...

Before each step: TaskUpdate → status: "in_progress" After each step: TaskUpdate → status: "completed" On context recovery: TaskList → resume from last incomplete step

Respond in Chinese per CLAUDE.md. Deep analysis for complex problems and decisions.

Problem

Analysis Protocol

Step 1: Scope Check

If the problem is ambiguous or underspecified, ask up to 3 clarifying questions via AskUserQuestion before proceeding. If the problem is simple enough for a direct answer, skip the full framework and respond concisely — mark all remaining tasks as completed with note "skipped: simple answer path".

Step 2: Evidence Gathering

For any factual claim about technology, APIs, or best practices, verify via Context7/Exa MCP before asserting. Label each assertion:

Fact: Verified from official source
Inference: Deduced from facts
Speculation: Needs verification (list verification steps)

Step 3: Multi-Perspective Analysis

Generate at least 3 distinct approaches. For each, analyze through whichever lenses are relevant:

Technical: Feasibility, scalability, security, maintainability
Business: Value, cost, time-to-market, competitive advantage
User: Needs, experience, edge cases, accessibility
System: Integration, dependencies, emergent behaviors

Step 4: Adversarial Stress-Testing

Apply these techniques to pressure-test your reasoning:

Steel Man: Before recommending, build the strongest possible case FOR the option you're inclined to reject
Pre-Mortem: Assume the recommended option has failed in 6 months. List the 3 most likely causes
Sensitivity: Identify which assumption, if wrong, would reverse your recommendation
Second-Order: What new problems does the recommended option create 6-12 months out?

Read the full file on GitHub · 102 lines

Changes

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.

2mo ago First seen · 102 lines · 12 tokens per session scan A da16b2ed8f86

Subscribe to this mod's changes

ultra-think is a command published in the GitHub repository rocky2431/ultra-builder-pro (11 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 909 once invoked, about $0.0000 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-08-30.

Planning

ultra-think next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ultra-thinkrocky2431/ultra-builder-pro	Command	11	3mo ago	MIT	A	12	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code