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 WillInvest/ClaudeX --skill ultra-researchgit clone --depth 1 https://github.com/WillInvest/ClaudeXWrote 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/willinvest/claudex/ultra-research)<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.
<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>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.00158 | $0.02166 |
| Opus 5 | $0.00079 | $0.01083 |
| Sonnet 5 | $0.00032 | $0.00433 |
| Haiku 4.5 | $0.00016 | $0.00217 |
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.
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 — 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
- 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.
- 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 ofprompts/codex-research.md, placeholders filled, including--writeand the absolute target$RUNDIR/20-report-codex.md. Prefer background. - Claude (inline): run
claudex:deep-researchyourself on the same refined question. When it finishes, write its verified report to$RUNDIR/10-report-claude.mdwith 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):
If the post-loop# 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. fireadycheck fails → DEGRADED branch A (below).
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.
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 · 148 lines · 158 tokens per session scan A 160db6793cf2
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.
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.
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.
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.
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.
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.
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.