A command that fills missing pages and links in an Obsidian wiki built from project sources. It organizes information around the project's main topics and checks the result.

Use it to ingest repository material, create topic overview pages, resolve broken links, expand thin pages, and verify the wiki's structure.

It removes empty pages and broken wiki links that make a knowledge graph hard to follow. It also reduces the need to find and repair gaps by hand.

fill-gaps — Command for Claude Code by odere-pro

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/odere-pro/claude-wiki-pages-plugin

Made for: Claude Code.

Or install claude-wiki-pages, the plugin that ships this one along with the rest of its 26 skills, 5 commands, 17 agents, 7 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/odere-pro/claude-wiki-pages-plugin/fill-gaps/github.svg)](https://agentmods.dev/commands/odere-pro/claude-wiki-pages-plugin/fill-gaps)

Your own site

<a href="https://agentmods.dev/commands/odere-pro/claude-wiki-pages-plugin/fill-gaps"><img src="https://agentmods.dev/badge/commands/odere-pro/claude-wiki-pages-plugin/fill-gaps/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/odere-pro/claude-wiki-pages-plugin/fill-gaps"><img src="https://agentmods.dev/badge/commands/odere-pro/claude-wiki-pages-plugin/fill-gaps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 603 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.

Model	Per session	Once invoked
Fable 5.1	$0.00045	$0.00603
Opus 5	$0.00023	$0.00302
Sonnet 5	$0.00009	$0.00121
Haiku 4.5	$0.00005	$0.00060

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

Security

Grade A, and why

fill-gaps 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 9d 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/fill-gaps.md · 52 lines

How it starts

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

/claude-wiki-pages:fill-gaps

Turn a thin or hole-y vault into a complete, gap-free wiki: zero dangling wikilinks (no empty graph nodes), no empty pages, and a graph whose nodes and edges concentrate around the project's core topic clusters.

What this command does

Invokes the fill-gaps skill, which:

Resolves the vault + repo and asserts they match (guards against writing the wrong vault).
Materializes the bundled gap-fill workflow into the project's .claude/workflows/fill-knowledge-gaps.mjs (idempotent — only if absent/changed; never clobbers a user-modified copy).
Runs it via the Workflow tool. The workflow drives the existing ingest, curator, and polish agents through eight sequential, git-checkpointed phases: stage curated repo sources → ingest by topic → author topic hub pages → resolve every dangling link (create real pages / fix links / prose-ify) → enrich thin pages → heal + polish → measure.
Reports baseline → final: dangling count (target 0), engine verify status, node/edge concentration on the topic clusters, and the per-cluster breakdown.

When to use this command

The Obsidian graph shows empty grey nodes (dangling [[links]]).
The wiki is thin on the core topics and you want it filled from the repo.
You want the graph re-centered on a fixed set of topic clusters.

Safe to re-run — every phase is git-checkpointed (git revert any phase) and the run is idempotent. This command writes to the vault, so it is gated like ingest and never auto-fires.

Companion commands

/claude-wiki-pages:wiki — the top-level entry; routes "complete the wiki / fill the gaps" intent here automatically.
/claude-wiki-pages:lint — read-only structural audit (does not fill gaps).

Specification anchor

Skill: skills/fill-gaps/SKILL.md. Decision record: docs/adr/ADR-0027-fill-gaps-and-graph-quality.md.

Read the full file on GitHub · 52 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.

9d ago First seen · 52 lines · 45 tokens per session scan A 748b63d1c104

Subscribe to this mod's changes

fill-gaps is a command published in the GitHub repository odere-pro/claude-wiki-pages-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 603 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.

Claude Code Writing and docs agentic ai-agents claude-code-agents claude-code-plugin claude-code-skills

psql-query

Run ad-hoc PostgreSQL analytics queries against dev/test database.

oliver-kriska/claude-elixir-phoenix · 16 tokens

discover

Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.

avelikiy/great_cto · 44 tokens

coding-audit

Medical-coding / revenue-cycle compliance audit. Invokes rcm-reviewer to assess autonomous ICD-10-CM / CPT / HCPCS coding for False Claims Act exposure (upcoding/unbundling), NCCI edits + MUEs, medical necessity (LCD/NCD), modifier discipline, HIPAA minimum-necessary — and force a certified-coder (CPC/CCS) sign-off.

avelikiy/great_cto · 81 tokens

fill-gaps