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 schub-tech/llm-ideation-wiki --skill research-deepgit clone --depth 1 https://github.com/schub-tech/llm-ideation-wikiWrote 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/schub-tech/llm-ideation-wiki/research-deep)<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>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.00079 | $0.00658 |
| Opus 5 | $0.00039 | $0.00329 |
| Sonnet 5 | $0.00016 | $0.00132 |
| Haiku 4.5 | $0.00008 | $0.00066 |
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.
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 integrationsection: 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.
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.
- 8d ago First seen · 26 lines · 79 tokens per session scan A b4bd4297d88c
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.
Other skills, from other repositories
duckduckgo-search
Free keyless web, news, and image search via ddgs.
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…