research

research is a skill for Claude Code, Codex from parcadei/ContinuousClaudeV4.7. It costs 18 tokens per session (1,364 once invoked), scanned A, original, MIT.

A research workflow using Ouros RLM, a sandboxed Python workspace that keeps variables and reasoning state between runs.

In plain words
What is it for?
Use it to explore unfamiliar questions, search external sources, call other agents or language models, and save, resume, or branch research sessions.
Why use it?
It helps preserve context during open-ended investigation and reduces the need to repeat large amounts of information in each step.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/parcadei/continuousclaudev4.7/research
Any agent
npx skills add parcadei/ContinuousClaudeV4.7 --skill research
Clone the repo
git clone --depth 1 https://github.com/parcadei/ContinuousClaudeV4.7

Made for: Claude Code, Codex.

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 research

README.md
[![agentmods](https://agentmods.dev/badge/skills/parcadei/continuousclaudev4.7/research.svg)](https://agentmods.dev/skills/parcadei/continuousclaudev4.7/research)
Your own site
<a href="https://agentmods.dev/skills/parcadei/continuousclaudev4.7/research"><img src="https://agentmods.dev/badge/skills/parcadei/continuousclaudev4.7/research.svg" alt="Measured on agentmods" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,364 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00018 $0.01364
Opus 5 $0.00009 $0.00682
Sonnet 5 $0.00004 $0.00273
Haiku 4.5 $0.00002 $0.00136

Measured 5d ago against content hash 213a28ac6b6a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 5d 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.

.claude/skills/research/SKILL.md · 120 lines

How it starts

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

Use when you need to explore, reason through an idea, or research something you don't already know the answer to. Unlike /autonomous (which drives toward known goals), /research is for open-ended investigation where the destination isn't clear yet.

Ouros is a sandboxed Python REPL that persists variables across executions, supports fork/save/resume, and bridges to external functions (exa search, nia docs, llm_call, agent_call). Context lives in the REPL heap — not in your conversation window — so you can reason over large amounts of data without burning tokens.

Harness location: tools/ouros_harness.py

Core commands:

# Execute research code in a named session
python tools/ouros_harness.py --file /tmp/research.py \
  --session {topic} --storage continuum/research

# Resume a previous session (loads saved state, then runs new code)
python tools/ouros_harness.py --file /tmp/next-step.py \
  --session {topic} --storage continuum/research --load

# Fork a session for parallel exploration
python tools/ouros_harness.py --session {topic} \
  --storage continuum/research --fork {topic}-branch-a

# Inspect session state
python tools/ouros_harness.py --session {topic} \
  --storage continuum/research --list-vars

# Extract a variable as JSON
python tools/ouros_harness.py --session {topic} \
  --storage continuum/research --get-var findings

Available functions inside the REPL:

Research: exa_search(query, num_results, with_text, domains, start_date), nia_search(query, repositories, data_sources), nia_universal(query, limit), nia_web(query), nia_package(package, query, registry), nia_package_grep(package, pattern, registry), research_package(package, version, registry), nia_help().

RLM recursive calls: llm_call(prompt, model, backend, max_tokens, system, temperature) — stateless LM sub-query. agent_call(prompt, agent, model, max_turns, timeout, cwd, isolated) — headless agent with full tool access.

Filesystem: read_file(path), write_file(path, content), glob_files(pattern, path), run_command(cmd, timeout).

How to use this skill:

Write a Python program that decomposes the research question, calls external functions, stores intermediate results as variables, and produces a telegraphic artifact as final output. The program runs inside Ouros — all variables persist in the session and can be inspected, forked, or resumed later.

The key RLM property: sub-agents (via agent_call) and LM queries (via llm_call) are functions called from within the REPL. Results flow back into the program as return values, not as context injected into your conversation. This means you can orchestrate multiple agents, aggregate their outputs, reason over the combined data — all without any of it touching your token budget.

Example research program:

# Research: What auth patterns does this codebase use?

# 1. Gather data from multiple sources
codebase_auth = agent_call(
    "Search this codebase for authentication patterns. "
    "List every auth-related file with a one-line summary. "
    "Include: middleware, token validation, session handling, OAuth.",
    agent="claude-code", model="sonnet", max_turns=5
)

best_practices = exa_search(
    "modern authentication patterns 2026 JWT OAuth session",
    num_results=5, with_text=True
)

docs = nia_search("authentication middleware best practices")

# 2. All results are now REPL variables — no tokens spent in conversation

# 3. Synthesize via LLM sub-call (only sees relevant slices)
synthesis = llm_call(
    f"Given these codebase auth patterns:\n{codebase_auth}\n\n"
    f"And these best practices:\n{docs.get('answer', '')}\n\n"
    "Write a telegraphic assessment: what's good, what's missing, "
    "what should change. Be specific with file:line references.",
    model="claude-sonnet-4-6", backend="anthropic", max_tokens=2000
)

# 4. Store as artifact
findings = {
    "question": "What auth patterns does this codebase use?",
    "synthesis": synthesis,
    "sources": {
        "codebase": codebase_auth[:500],
        "exa_results": len(best_practices.get("results", [])),
        "nia_answer": docs.get("answer", "")[:300],
    },
}

# 5. Write telegraphic artifact for /autonomous or handoff consumption
write_file("continuum/research/auth-patterns/findings.md", f"""# Auth Patterns Research

{synthesis}

## Sources
- Codebase scan: {len(codebase_auth)} chars of analysis
- Exa: {len(best_practices.get('results', []))} results
- Nia docs: indexed answer available
""")

print(synthesis)

Read the full file on GitHub · 120 lines

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. 5d ago First seen · 120 lines · 18 tokens per session scan A 213a28ac6b6a

Subscribe to this mod's changes

research is a skill published in the GitHub repository parcadei/ContinuousClaudeV4.7 (48 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 1,364 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens