research-deep

research-deep is a skill for Claude Code, Codex from schub-tech/llm-ideation-wiki. It costs 79 tokens per session (658 once invoked), scanned A, original, MIT.

A web-research workflow that answers specific questions and saves source notes to Notion, a workspace for organizing documents.

In plain words
What is it for?
Use it to investigate questions, search for reliable sources, read them, and create raw research notes in Notion.
Why use it?
It prevents repeated searches and keeps research findings in one place for later use. It also helps turn a confirmed research plan into documented evidence.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; installed under .agents/ (shared by several agents).

Good fit Use it to investigate questions, search for reliable sources, read them, and create raw research notes in Notion.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/schub-tech/llm-ideation-wiki/research-deep
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 schub-tech/llm-ideation-wiki --skill research-deep
Clone the repo
git clone --depth 1 https://github.com/schub-tech/llm-ideation-wiki

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-deep

README.md
[![agentmods](https://agentmods.dev/badge/skills/schub-tech/llm-ideation-wiki/research-deep.svg)](https://agentmods.dev/skills/schub-tech/llm-ideation-wiki/research-deep)
Your own site
<a href="https://agentmods.dev/skills/schub-tech/llm-ideation-wiki/research-deep"><img src="https://agentmods.dev/badge/skills/schub-tech/llm-ideation-wiki/research-deep.svg" alt="Measured on agentmods" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 658 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.00079 $0.00658
Opus 5 $0.00039 $0.00329
Sonnet 5 $0.00016 $0.00132
Haiku 4.5 $0.00008 $0.00066

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

Security

Grade A, and why

research-deep 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 8d 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.

.agents/skills/research-deep/SKILL.md · 26 lines

What it actually says

Run targeted web research on one or more research questions and produce raw notes, then propose distilling them into the wiki via docs/agent/workflows.md. Maintaining the wiki is the LLM's job, not the user's — don't leave the raw notes sitting unintegrated.

Identify the question. From a /find-gaps plan or a direct user prompt. If vague, narrow it before searching ("research the market" → "What 2024-2025 sources support or contradict the TAM figure cited in the overview's Market section?"). Read the relevant Notion raw/<idea-slug>/ page and raw/shared/ first to avoid retreading ground — if a recent note already covers the question, say so and ask the user whether to skip, supplement, or refresh.

Plan and execute searches. Draft 2-4 targeted queries per question and run them. Read the most relevant sources end-to-end, not just snippets — snippets lose date and context. For multiple research questions in one session, consider launching one sub-agent per question so they run concurrently; each sub-agent owns its question end-to-end (queries, source reading, raw-note write) and returns when done. The parent agent then compiles the report-back.

Write one raw source page per research question under the relevant Notion raw/<idea-slug>/ page, or under raw/shared/ if it applies across ideas. Title it with a date and topic, e.g. 2026-04-24 market pricing research. Each raw page should:

  • State the originating question at the top (one sentence).
  • Capture findings with source URL, publication date, and direct quote for every material claim.
  • Mark uncertain or contested claims as [uncertain] with a one-line reason.
  • Surface contradictions across sources explicitly instead of picking the most flattering one.
  • Distinguish facts (what a source says) from synthesis (what the agent concludes from multiple sources).
  • End with a ## Suggested wiki integration section: which idea overview / deep-dive section would update, and a one-line draft of the diff.

Report back. After all notes are written (or all sub-agents have returned), list them with a one-line summary each, ordered by what would most move the verdict. Flag findings that confirm a load-bearing claim, findings that kill one, and questions where the search returned no useful evidence.

Suggest the ingest pass. Once the raw pages exist, propose running the ingest workflow in docs/agent/workflows.md next. Offer to do it directly. Don't leave new evidence as raw-only.

Cite real URLs only — never fabricate one. If a search returns nothing useful, say so explicitly rather than padding the note with adjacent content.

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. 8d ago First seen · 26 lines · 79 tokens per session scan A b4bd4297d88c

Subscribe to this mod's changes

research-deep is a skill published in the GitHub repository schub-tech/llm-ideation-wiki (11 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 658 once invoked, about $0.0004 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