wiki-ideate

wiki-ideate is a command for Claude Code from Spark-To-Paper-Skills/paper-wiki. It costs 30 tokens per session (5,580 once invoked), scanned A, original, MIT.

A read-only research-idea command for a compiled Paper Wiki. It examines the project's goals, papers, concepts, and gaps to refine an existing research gap or identify missing coverage.

In plain words
What is it for?
Use it for exploratory research questions, a named knowledge gap, or a candidate problem, but not for course wikis.
Why use it?
It keeps ideation tied to the project's cited material and checks whether an apparent problem may already have been solved.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

Part of the paper-wiki plugin — 1 skill, 8 commands, 4 agents, 1 hook shipped together

Good fit Use it for exploratory research questions, a named knowledge gap, or a candidate problem, but not for course wikis.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/spark-to-paper-skills/paper-wiki/wiki-ideate
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.

Clone the repo
git clone --depth 1 https://github.com/Spark-To-Paper-Skills/paper-wiki

Made for: Claude Code.

Or install paper-wiki, the plugin that ships this one along with the rest of its 1 skill, 8 commands, 4 agents, 1 hook.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/spark-to-paper-skills/paper-wiki/wiki-ideate/github.svg)](https://agentmods.dev/commands/spark-to-paper-skills/paper-wiki/wiki-ideate)
Your own site
<a href="https://agentmods.dev/commands/spark-to-paper-skills/paper-wiki/wiki-ideate"><img src="https://agentmods.dev/badge/commands/spark-to-paper-skills/paper-wiki/wiki-ideate/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.

agentmods 80×15 button for wiki-ideate

Your own site · 80×15
<a href="https://agentmods.dev/commands/spark-to-paper-skills/paper-wiki/wiki-ideate"><img src="https://agentmods.dev/badge/commands/spark-to-paper-skills/paper-wiki/wiki-ideate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,580 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.00030 $0.05580
Opus 5 $0.00015 $0.02790
Sonnet 5 $0.00006 $0.01116
Haiku 4.5 $0.00003 $0.00558

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

Security

Grade A, and why

wiki-ideate 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 12d 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.

commands/wiki-ideate.md · 350 lines

How it starts

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

Run the paper-wiki wiki-ideate action. This file adapts the action to a Claude Code slash command.

  1. Read WIKI.md, then research.md and the current wiki/{papers,concepts,gaps} inventory.

  2. Stop for a course wiki; novelty-gap ideation is research-only.

  3. Resolve the argument to one of three paths — goal-focused, gap-focused, or exploratory. Ask the user when a name matches more than one file.

    • goal-focused: the argument names a wiki/field/problems.md candidate line, or an already-adopted goal card under wiki/field/problems/<goal-id>.md.
    • gap-focused (existing): the argument names a wiki/gaps/<id>.md file.
    • exploratory (existing): no argument.

    The goal-focused / exploratory split is a written-down criterion, not a feeling: attempt Q1 (extensional identity — can the opponent's already-reported result satisfy one instantiation of our main facet?) and Q4 (F11 standard — does the opponent's explicit conclusion sentence claim to have solved it?) against the candidate's problem statement, after a real retrieval-and-adjudication attempt. If both questions return a determinate result (problem-open, problem-solved, or partially-solved with criteria_delta), the statement "can be adjudicated for openness" — take the goal-focused path (step 5 below). If neither question can return a determinate result (e.g. the problem is too vague to name what "one instantiation of the main facet" even is), the statement "cannot be written out" — take the exploratory path instead: open a direction card, let a mechanism trace emerge from probing, and come back later.

    Late admission (补票) is explicitly legal: an exploratory direction card may, once a mechanism trace appears, retroactively adopt a goal. But late admission must run the full four-way diagnosis + openness adjudication in step 5 below — it is a hard constraint, not a suggestion, that it is forbidden to shortcut or waive any step because probe data already exists(不得因已有探针数据减免任何一步); probe data is reference-only and never itself constitutes adjudication evidence. This is the path that gives E3 ("idea 起于发现") its legitimate standing — it is no longer a residual quota, it is a named route.

  4. If fewer than three papers are compiled, warn that coverage is too thin and ask before continuing. Suggest wiki-compile or wiki-search-latest first. In an auto run (/wiki-auto-driven), do not ask: stop this ideation cleanly and append one INBOX row (coverage too thin).

  5. Goal-focused adoption flow (runs only when step 3 resolved to the goal-focused path; a late-admission/补票 candidate re-enters here and must run every sub-step below in full — see step 3's 补票 clause).

    i. Four-way diagnosis (四分诊断) — judge why the gap exists: gold-mine / dead-end / tool-missing / already-reworded (换词已做). The four categories are non-exclusive; multiple tags plus one primary cause are allowed. Check hidden-done first — semantic search across vocabulary; search_record is upgraded from "log what was searched" to search-then-record(先搜后记): the search runs first, the record follows, and even a zero-hit round still lands its query list as a search_record. Check tool-missing against the candidate's potential attack surface. The worker produces only a symmetric two-sided evidence brief (one column "why it matters", one column "why it isn't worth it" — never a single-sided brief): hiding a taste judgment inside an enum is the least honest move this design could make — the same architectural discipline as "no kill verdict" in the review layer and "a human reads the criterion directly" in the probe layer.

    ii. Human signs gold-mine or dead-end. In attended mode this verdict belongs to a human, never to the agent. In an auto run (/wiki-auto-driven), the agent renders the verdict itself and fills the column, signed 机签 (auto + 日期), with one wiki/INBOX.md row — a human may overrule it afterwards by normal editing.

Read the full file on GitHub · 350 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. 12d ago First seen · 350 lines · 30 tokens per session scan A f35e484cd815

Subscribe to this mod's changes

wiki-ideate is a command published in the GitHub repository Spark-To-Paper-Skills/paper-wiki (7 stars, last pushed 29d ago), licensed MIT. It adds 30 tokens to every session and 5,580 once invoked, about $0.0002 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.