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 skills add rocky2431/ultra-builder-pro --skill ultra-researchgit clone --depth 1 https://github.com/rocky2431/ultra-builder-proWrote 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/rocky2431/ultra-builder-pro/ultra-research)<a href="https://agentmods.dev/skills/rocky2431/ultra-builder-pro/ultra-research"><img src="https://agentmods.dev/badge/skills/rocky2431/ultra-builder-pro/ultra-research/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/rocky2431/ultra-builder-pro/ultra-research"><img src="https://agentmods.dev/badge/skills/rocky2431/ultra-builder-pro/ultra-research.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.00021 | $0.01651 |
| Opus 5 | $0.00010 | $0.00826 |
| Sonnet 5 | $0.00004 | $0.00330 |
| Haiku 4.5 | $0.00002 | $0.00165 |
Grade A, and why
ultra-research 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 11d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ultra Research v2 — Step-File Architecture
Overview
Transform vague ideas into complete, high-confidence specifications through progressive interactive discovery. Each research step is a self-contained instruction file loaded just-in-time for maximum LLM attention density.
Philosophy: Research is collaborative. Each decision validated with user before proceeding. All findings must have 90%+ confidence. Every claim needs a source.
WORKFLOW ARCHITECTURE
Core Principles
- Step-File Design: Each step is a self-contained .md file with full execution instructions
- Just-In-Time Loading: Only the current step file is in context — never load future steps
- Sequential Enforcement: Steps must be completed in order, no skipping
- Write-Immediately: Every step writes its output to the spec file BEFORE presenting to user
- User Gate: User must explicitly confirm [C] Continue before proceeding to next step
- State Tracking: Track progress via TaskCreate/TaskUpdate system
- Web-First: Every analysis step REQUIRES web search with citations. No search = no proceed.
Step Processing Rules
- READ COMPLETELY: Always read the entire step file before taking any action
- FOLLOW SEQUENCE: Execute all numbered sections in order
- SEARCH FIRST: Execute web searches BEFORE generating analysis
- WRITE IMMEDIATELY: Append content to spec file as soon as analysis is complete
- WAIT FOR INPUT: Present [C] Continue — halt and wait for user selection
- LOAD NEXT: When user confirms, Read the next step file and follow it
Critical Rules (NO EXCEPTIONS)
- NEVER load multiple step files simultaneously
- ALWAYS read entire step file before execution
- NEVER skip steps or optimize the sequence
- ALWAYS write output to spec file before presenting to user
- ALWAYS halt at [C] Continue and wait for user input
- NEVER proceed without user confirmation
- NEVER rely solely on training data — web search is mandatory for factual claims
What ships with it
17 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.
- steps/step-00-problem-validation.md 5.9 KB
- steps/step-01-opportunity-discovery.md 5.7 KB
- steps/step-02-market-assessment.md 6.3 KB
- steps/step-03-competitive-landscape.md 6.7 KB
- steps/step-04-product-strategy.md 6.5 KB
- steps/step-05-assumptions-validation.md 7.6 KB
- steps/step-10-user-personas.md 5.3 KB
- steps/step-11-user-scenarios.md 5.3 KB
- steps/step-20-user-stories.md 4.4 KB
- steps/step-21-features-scope.md 4.4 KB
- steps/step-22-success-metrics.md 5.9 KB
- steps/step-30-architecture-context.md 4.8 KB
- steps/step-31-solution-strategy.md 5.1 KB
- steps/step-32-building-blocks.md 5.4 KB
- steps/step-40-deployment.md 3.4 KB
- steps/step-41-quality-risks.md 4.1 KB
- steps/step-99-synthesis.md 6.3 KB
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.
- 11d ago First seen · 157 lines · 21 tokens per session scan A fd8e8006db2e
ultra-research is a skill published in the GitHub repository rocky2431/ultra-builder-pro (11 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,651 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…