ultra-research

ultra-research is a skill for Claude Code from WillInvest/ClaudeX. It costs 158 tokens per session (2,166 once invoked), scanned A, original, MIT.

A two-researcher process for investigating an important question independently, checking each other's sources, and combining the results. It is meant for cases where trustworthy evidence matters.

In plain words
What is it for?
Use it for high-stakes policy, financial, or factual research; requests for cross-checked research; or topics where an earlier report had unreliable citations.
Why use it?
It reduces the chance that one research run relies on weak, missing, or poorly matched citations. It also makes disagreements between the two investigations visible.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; mentions Codex.

Part of the claudex plugin — 5 skills, 2 hooks shipped together

Good fit Use it for high-stakes policy, financial, or factual research; requests for cross-checked research; or topics where an earlier report had unreliable citations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/willinvest/claudex/ultra-research
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.

Any agent
npx skills add WillInvest/ClaudeX --skill ultra-research
Clone the repo
git clone --depth 1 https://github.com/WillInvest/ClaudeX

Made for: Claude Code.

Or install claudex, the plugin that ships this one along with the rest of its 5 skills, 2 hooks.

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.

agentmods badge for ultra-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/willinvest/claudex/ultra-research/github.svg)](https://agentmods.dev/skills/willinvest/claudex/ultra-research)
Your own site
<a href="https://agentmods.dev/skills/willinvest/claudex/ultra-research"><img src="https://agentmods.dev/badge/skills/willinvest/claudex/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.

agentmods 80×15 button for ultra-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/willinvest/claudex/ultra-research"><img src="https://agentmods.dev/badge/skills/willinvest/claudex/ultra-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 158 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,166 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00158 $0.02166
Opus 5 $0.00079 $0.01083
Sonnet 5 $0.00032 $0.00433
Haiku 4.5 $0.00016 $0.00217

Measured 10d ago against content hash 160db6793cf2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 10d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/test_vault.py, scripts/vault.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/ultra-research/SKILL.md · 148 lines

How it starts

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

ultra-research

$SKILL_DIR is this skill's directory. The Python helper is scripts/vault.py; prompts are in prompts/. Read each prompt when you reach its stage.

When to use (routing)

Prefer plain claudex:deep-research by default. Use ultra-research only when: the question is high-stakes (policy/financial/factual gravity); the user explicitly asks for dual-model or cross-verified research; or a prior deep-research run on the topic returned mixed/unreliable citation integrity.

Setup

  1. Disambiguate like deep-research: if the question is underspecified, ask 2–3 clarifying questions, then proceed; else state one interpretation and proceed. Never block mid-run after this point.
  2. Resolve paths and the run id:
    VAULT="$(python3 "$SKILL_DIR/scripts/vault.py" vaultpath)"
    REFINED_QUESTION="$(cat <<'EOF'
    

Stage 1 — independent research (parallel)

  • Codex (background): dispatch Agent(subagent_type: codex:codex-rescue) with the text of prompts/codex-research.md, placeholders filled, including --write and the absolute target $RUNDIR/20-report-codex.md. Prefer background.
  • Claude (inline): run claudex:deep-research yourself on the same refined question. When it finishes, write its verified report to $RUNDIR/10-report-claude.md with the report frontmatter (author-model: claude, note-type: report, degraded: false, tags: [ultra-research, report]).
  • Join: poll for the Codex file until ready or the deadline. Resolve the per-stage timeout via the helper (handles scalar or object codexTimeoutMs):
    # Stage-1 research default: 20 min (1,200,000 ms) unless config overrides it.
    DEADLINE=$(( $(date +%s%3N) + $(python3 "$SKILL_DIR/scripts/vault.py" timeout --stage research) ))
    until python3 "$SKILL_DIR/scripts/vault.py" ready "$RUNDIR/20-report-codex.md"; do
      [ "$(date +%s%3N)" -ge "$DEADLINE" ] && break
      sleep 10
    done
    if ! python3 "$SKILL_DIR/scripts/vault.py" ready "$RUNDIR/20-report-codex.md"; then
      # Execute DEGRADED branch A.
    fi
    
    If the post-loop ready check fails → DEGRADED branch A (below).

Read the full file on GitHub · 148 lines

Files

What ships with it

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

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.

  1. 10d ago First seen · 148 lines · 158 tokens per session scan A 160db6793cf2

Subscribe to this mod's changes

ultra-research is a skill published in the GitHub repository WillInvest/ClaudeX (4 stars, last pushed 3mo ago), licensed MIT. It adds 158 tokens to every session and 2,166 once invoked, about $0.0008 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.

Related

Other skills, from other repositories

brainstorming-research-ideas

Guides researchers through structured ideation frameworks to discover high-impact research directions. Use when exploring new problem spaces, pivoting between projects, or seeking novel angles on existing work.

Orchestra-Research/AI-Research-SKILLs · 43 tokens

pdlc-feature

An automated workflow for taking a new software feature from a description or requirements document through requirements, design, testing, implementation, review, and release preparation. It keeps one feature ID across the documents and requires tests before implementation.

kanfu-panda/pdlc-skills · 30 tokens

pdlc-quality

A quality gate that runs configured coverage, end-to-end, and lint checks, compares their real results with declared targets, and creates a report for human approval.

kanfu-panda/pdlc-skills · 0 tokens

pdlc-review

A code-review workflow that checks an implementation against its design, tests, coding rules, quality checks, and common security concerns. It requires the implementation to exist and its tests to pass before reviewing it.

kanfu-panda/pdlc-skills · 13 tokens

pdlc-adopt

A tool for bringing an existing software project into a documented development process. It scans the project, identifies its services, applications, technologies, databases, and APIs, and can create baseline documents without changing code.

kanfu-panda/pdlc-skills · 12 tokens

pdlc-test-setup

A project setup workflow that finds the programming language, package manager, test framework, and available checking tools, then records verified commands in test-commands.yml. It can also create test folders and connect local hooks.

kanfu-panda/pdlc-skills · 0 tokens