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/heyAyushh/staccWrote 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/heyayushh/stacc/ultrathink)<a href="https://agentmods.dev/commands/heyayushh/stacc/ultrathink"><img src="https://agentmods.dev/badge/commands/heyayushh/stacc/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/commands/heyayushh/stacc/ultrathink"><img src="https://agentmods.dev/badge/commands/heyayushh/stacc/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.00000 | $0.00290 |
| Opus 5 | $0.00000 | $0.00145 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
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 9d 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.
What it actually says
ultrathink - Deep Reasoning Mode
When invoked, engage maximum cognitive depth for complex problems.
Protocol
1. Clarify First
Before any implementation, use the AskUserQuestion subagent to:
- Confirm understanding of the core problem
- Surface hidden assumptions
- Identify edge cases and constraints
- Validate success criteria
2. Think Deeply
- Break the problem into atomic components
- Consider multiple approaches with trade-offs
- Reason through edge cases and failure modes
- Think about security, performance, and maintainability
- Document your reasoning chain explicitly
3. Implement Carefully
- Write code incrementally with clear intent
- Use meaningful names that reveal purpose
- Handle errors explicitly at boundaries
- Keep solutions minimal—no speculative features
4. Verify Rigorously
After implementation, invoke the verifier subagent to:
- Confirm the solution addresses the original problem
- Test critical paths and edge cases
- Validate no regressions were introduced
- Ensure code quality standards are met
Subagent Usage
Task(subagent_type="AskUserQuestion", prompt="Clarify X before proceeding...")
Task(subagent_type="verifier", prompt="Verify implementation of X...")
Mindset
- Prefer correctness over speed
- Question assumptions ruthlessly
- Make implicit requirements explicit
- Leave code better than you found it
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.
- 9d ago First seen · 47 lines · 0 tokens per session scan A 2e89a3814e1b
ultrathink is a command published in the GitHub repository heyAyushh/stacc (3 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 290 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.