agentmods.dev

wiki-research

wiki-research is a skill for Claude Code, Codex from badwally/TheKnowledge. It costs 21 tokens per session (503 once invoked), scanned A, original, MIT.

A structured research tool that investigates a question across multiple sources and saves the result as a wiki synthesis page.

In plain words
What is it for?
Use it to check existing wiki coverage, review a proposed source plan, run the research, and file the resulting synthesis.
Why use it?
It organizes source searching and helps turn scattered findings into a stored research summary.

Skill for Claude CodeCodex

not rated 23 1mo ago A scan 21 tokens original MIT
View the source file badwally/TheKnowledge
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/badwally/theknowledge/wiki-research
Any agent
npx skills add badwally/TheKnowledge --skill wiki-research
Clone the repo
git clone --depth 1 https://github.com/badwally/TheKnowledge

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 wiki-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/badwally/theknowledge/wiki-research.svg)](https://agentmods.dev/skills/badwally/theknowledge/wiki-research)
Your own site
<a href="https://agentmods.dev/skills/badwally/theknowledge/wiki-research"><img src="https://agentmods.dev/badge/skills/badwally/theknowledge/wiki-research.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 503 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.00021 $0.00503
Opus 5 $0.00010 $0.00251
Sonnet 5 $0.00004 $0.00101
Haiku 4.5 $0.00002 $0.00050

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

Security

Grade A, and why

wiki-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 4d 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/wiki-research/SKILL.md · 56 lines

What it actually says

What This Does

Takes a research question, fans out across search adapters, filters candidates, and files a synthesis page via the gateway. Uses wiki research + wiki query.

Reference conventions: WIKI.md § 5 (query workflow), § 7 (synthesis pages).

Usage

/wiki-research "How does GLP-1 affect dopamine reward circuits?"
/wiki-research "What are the risks of AI agents in clinical settings?" --domain edge-ai-agentic

Execution Steps

  1. Check existing coverage: Run wiki search "<key terms>" and scan index.md for related synthesis pages. If an answer already exists, link to it and stop unless the user wants a fresh synthesis.

  2. Scoped research: Run:

    .venv/bin/wiki research "<question>" [--domain <slug>] --review

    This fans out search, filters candidates, and builds a query plan.

  3. Review plan: The --review flag surfaces the proposed source set. Confirm or adjust before executing.

  4. Execute:

    .venv/bin/wiki research "<question>" --execute <plan-id>

    Or use the shorthand: .venv/bin/wiki query "<question>" [--domain <slug>]

  5. Inspect output: The gateway writes a draft synthesis page to wiki/synthesis/<slug>.md. Read it and verify:

    • synthesizes: frontmatter lists source IDs
    • ## Sources cited section has [[sources/...]] links
    • Key claims are citation-grounded

  6. Finalize: If citations are complete, run wiki finalize on the page. Otherwise leave as draft and note the gap.

Key constraints

  • wiki query writes a wiki page — it is a write op. Plan before running (WIKI.md § 9).
  • Do not call NotebookLM tools directly. Route through wiki nlm-* commands (WIKI.md § 9).
  • Synthesis pages require synthesizes: frontmatter per ONT-11; validator warns if absent.
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. 4d ago First seen · 56 lines · 21 tokens per session scan A 92484e93746d

Subscribe to this mod's changes

wiki-research is a skill published in the GitHub repository badwally/TheKnowledge (23 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 503 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.

ResearchWriting and docs
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

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 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