research-gap

research-gap is a command for Claude Code from akougkas/wtf-p. It costs 18 tokens per session (1,243 once invoked), scanned A, a copy of add-todo, MIT.

A literature-research command for investigating an open question in one paper section. It synthesizes sources, evidence, common practices in the field, and possible gaps.

In plain words
What is it for?
Use it to create source and evidence records, research a section, and update that section's research context.
Why use it?
It helps replace an unsupported research gap with a documented, defensible position based on literature and domain conventions.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the wtfp plugin — 36 commands, 3 hooks shipped together

Good fit Use it to create source and evidence records, research a section, and update that section's research context.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add akougkas/wtf-p
Claude Code
/plugin install wtfp

Made for: Claude Code.

Or install wtfp, the plugin that ships this one along with the rest of its 36 commands, 3 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/akougkas/wtf-p/research-gap/github.svg)](https://agentmods.dev/commands/akougkas/wtf-p/research-gap)
Your own site
<a href="https://agentmods.dev/commands/akougkas/wtf-p/research-gap"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/research-gap/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 research-gap

Your own site · 80×15
<a href="https://agentmods.dev/commands/akougkas/wtf-p/research-gap"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/research-gap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,243 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 80% copy Near-identical to another mod 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.00018 $0.01243
Opus 5.5 $0.00007 $0.00497
Sonnet 5.5 $0.00004 $0.00249
Haiku 4.5 $0.00002 $0.00124

Measured 23d ago against content hash 0323c5c75aad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

research-gap 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 23d 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.

Origin

This is a copy

80% identical to add-todo — 53 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

vendors/claude/commands/research-gap.md · 82 lines

How it starts

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

Research a section gap

@${CLAUDE_PLUGIN_ROOT}/project/README.md @${CLAUDE_PLUGIN_ROOT}/skills/wtfp-research-literature/SKILL.md @${CLAUDE_PLUGIN_ROOT}/skills/wtfp-research-literature/references/actions.md

Record contract

Read: project://manifest, project://config, project://decisions, project://structure/outline, project://sections/{section}, project://sections/{section}/context, project://sources/{source}, project://evidence/{evidence}. Produce: project://sources/{source} (create), project://evidence/{evidence} (create), project://sections/{section}/research (create), project://sections/{section} (update).

Resolve every logical URI through the host adapter. Portable v1 JSON records are the source of truth: schema-validate before a write, preserve stable IDs, update revision and timestamps where required, and replace records atomically. Never pass a literal logical URI to a shell command or infer record state from a legacy Markdown control file.

Manuscript prose and supporting context, research, plan, review, summary, handoff, and deliverable artifacts retain their authored format (normally Markdown). Link them from the relevant v1 record; do not convert manuscript prose into project-state JSON.

Procedure

  1. Resolve the research question and section scope against locked/deferred decisions; agree on depth and source constraints.
  2. Prefer an operator-configured, trusted read-only CiteNexus MCP connection for bounded public metadata searches when the host has already authorized it. In an explicitly selected full-auto host session for this research action, the bundled CiteNexus dispatcher may also search the free no-key public indexes crossref, datacite, europe_pmc, and arxiv without a second per-query author gate; use only selected relevant indexes with an explicit --providers list. Record provider IDs, queries, date, and result limits; never send unpublished manuscript text or private notes as search terms. For any other route, first obtain explicit author approval naming the providers and bounded query set. Results remain candidates and this action performs no bibliography write. Verify source identity and inspection depth, and separate source records from claim-level evidence.
  3. Synthesize supported, conflicting, and missing evidence into a Markdown research artifact; link new records and disclose limitations.

Read the full file on GitHub · 82 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. 23d ago Changed 0323c5c75aad
  2. 29d ago Changed 292454414eb9
  3. 1mo ago First seen · 82 lines · 18 tokens per session scan A a99892c6f728

Subscribe to this mod's changes

research-gap is a command published in the GitHub repository akougkas/wtf-p (20 stars, last pushed 11d ago), licensed MIT. It adds 18 tokens to every session and 1,243 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 80% identical to add-todo, differing in 53 lines, and is treated as a copy.