Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add husniadil/ekstend/plugin install ultrathinkWrote 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/skills/husniadil/ekstend/ultrathink)<a href="https://agentmods.dev/skills/husniadil/ekstend/ultrathink"><img src="https://agentmods.dev/badge/skills/husniadil/ekstend/ultrathink/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/skills/husniadil/ekstend/ultrathink"><img src="https://agentmods.dev/badge/skills/husniadil/ekstend/ultrathink.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.00024 | $0.00626 |
| Opus 5 | $0.00012 | $0.00313 |
| Sonnet 5 | $0.00005 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
ultrathink 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 10d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UltraThink - Sequential Thinking CLI
A tool for dynamic and reflective problem-solving through structured, sequential thoughts.
When to Use
Use this skill for:
- Breaking down complex problems (>3 reasoning steps)
- Planning and design with room for revision
- Architecture decisions with multiple trade-offs
- Algorithm design and optimization
- Debugging multi-layered issues
- Analysis that might need course correction
Do NOT use for:
- Simple one-step answers
- Straightforward code edits
- Basic file operations
- Simple factual questions
Instructions
- Start a session with initial thought and estimated total
- Continue session using
session_idfrom response - Use
--confidenceto track uncertainty (0.0-1.0) - Revise thoughts with
--is-revision --revises <num> - Branch to explore alternatives with
--branch-from <num> --branch-id <name> - Track assumptions with
--assumptions,--depends-on,--invalidates - Monitor
risky_assumptionsin response - Continue until
next_thought_neededis false
Quick Start
# Start new session
uv run ${CLAUDE_PLUGIN_ROOT}/skills/ultrathink/scripts/ultrathink.py -t "Analyzing the problem..." -n 5
# Continue session
uv run ${CLAUDE_PLUGIN_ROOT}/skills/ultrathink/scripts/ultrathink.py -t "Next step..." -n 5 -s <session-id>
# With confidence
uv run ${CLAUDE_PLUGIN_ROOT}/skills/ultrathink/scripts/ultrathink.py -t "I believe X is correct" -n 3 -c 0.8
# With assumption
uv run ${CLAUDE_PLUGIN_ROOT}/skills/ultrathink/scripts/ultrathink.py -t "Assuming Redis available" -n 3 \
--assumptions '[{"id":"A1","text":"Redis is available"}]'
Example Session
Thought 1 (confidence: 0.6): "Analyzing access patterns for caching strategy..."
Thought 2 (confidence: 0.7): "Two approaches: LRU or LFU..."
Thought 3 (revision of 2): "Should also consider TTL-based expiration..."
Thought 4 (branch from 2): "Exploring hybrid LRU+TTL approach..."
Thought 5 (confidence: 0.95): "Hybrid approach recommended."
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 70 lines · 24 tokens per session scan A 0b86acd0eba2
ultrathink is a skill published in the GitHub repository husniadil/ekstend (1 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 626 once invoked, about $0.0001 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 skills, from other repositories
codex
Run the Codex CLI directly in the user's checkout for code analysis, refactoring, or automated editing without Claude Architect's verified delegation lifecycle.
commit
A guided process for committing code changes to Git. It checks the working tree, follows a conventional commit format, links a task when available, reviews the changes, and asks for approval.
x-multi-llm-align
A review process in which two sub-agents examine an API, data format, event schema, or workflow from their separate implementation perspectives. The user passes documents and feedback between them over multiple rounds.
design
Create a doc-as-code design package from a PRD or SPEC. Conditionally generates C4 diagrams (Context/Container/Component), sequence diagrams, ER diagram + Data Dictionary, OpenAPI 3.0, AsyncAPI 3.0, ADRs, domain glossary, state diagrams, and deployment view as Mermaid-rendered Markdown files. Use when PM mentions…
x-cr
A software-correctness investigation skill for finding why code behaves differently from what was expected. It uses evidence from code paths, specifications, tests, logs, and changes to assess possible causes.
explain
Use when user invokes /explain with a file path, directory path, function/class name, or natural language concept. Also triggers on "explain this", "how does X work", "walk me through". Produces a structured, layered explanation of what the code does, how it connects, and where to start if you need to change it. Do…