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.
/plugin marketplace add odere-pro/claude-wiki-pages-plugin/plugin install claude-wiki-pagesWrote 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/odere-pro/claude-wiki-pages-plugin/fill-gaps)<a href="https://agentmods.dev/skills/odere-pro/claude-wiki-pages-plugin/fill-gaps"><img src="https://agentmods.dev/badge/skills/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.
<a href="https://agentmods.dev/skills/odere-pro/claude-wiki-pages-plugin/fill-gaps"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-wiki-pages-plugin/fill-gaps.svg" alt="Reviewed on agentmods" width="80" 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.00106 | $0.01942 |
| Opus 5 | $0.00053 | $0.00971 |
| Sonnet 5 | $0.00021 | $0.00388 |
| Haiku 4.5 | $0.00011 | $0.00194 |
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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM Wiki — Fill Knowledge Gaps
Turn a thin or hole-y vault into a complete, gap-free wiki. Two problems this skill closes that ordinary ingest/lint do not:
- Dangling wikilinks —
[[Target]]references whose target resolves to no page. The Bun engine'sverifydoes not detect these (they pass0/0), yet they render as empty grey nodes in Obsidian's graph. This skill scans for them withscripts/graph-quality.shand drives them to zero. - Shallow / off-topic coverage — the graph should concentrate around the project's core topics, not scatter. This skill stages the high-signal repo sources, ingests them into topic clusters, and authors a hub page per topic so the majority of nodes and edges cluster there.
This skill orchestrates existing capabilities — the ingest, curator, and
polish agents plus the engine. It adds no new write logic of its own. Because a
Claude Code plugin cannot ship a runnable .mjs Workflow directly, this skill
carries the orchestration as a bundled template and materializes it into
the project on demand (the same pattern init uses for its vault scaffold),
then runs it with the Workflow tool.
When to invoke
- The Obsidian graph shows empty nodes / the wiki has broken
[[links]]. - Coverage of the core topics is thin and you want it filled from the repo.
- You want the graph re-centered on a fixed set of topic clusters.
- Re-run any time — every phase is git-checkpointed and the run is idempotent (prefer-update, no duplicate pages; resolved links stay resolved).
This skill writes to the vault (via the agents it dispatches), so it is gated
like ingest and is disable-model-invocation: true — invoked only on explicit
request, never auto-fired.
The capability contract (what the workflow does)
The bundled workflow runs eight sequential phases. Write phases are never
parallelized (they share one git tree and the index.md / log.md / folder
notes) and each self-checkpoints, so the whole run is a series of revertible
commits.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 137 lines · 106 tokens per session scan A 9e0dd1422382
fill-gaps is a skill published in the GitHub repository odere-pro/claude-wiki-pages-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 106 tokens to every session and 1,942 once invoked, about $0.0005 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.
Other skills, from other repositories
knowledge-maintain
This skill should be used when the user asks to fix, repair, or tidy one or more SPECIFIC named notes — 'fix these notes', 'fix the issues in [note]', 'add the missing relations to [note]', 'tidy up [note]', 'fix orphan [note]', 'apply the gardener findings for [note]'. Applies structural fixes (missing sections…
knowledge-garden
This skill should be used when the user asks to audit, health-check, or structurally validate one or more SPECIFIC named notes or a bounded topic cluster — 'audit these notes', 'check this note for orphans or broken links', 'fourth-wall check on [note]', 'validate the structure of [note]', 'spot-check [note]'. Runs a…
nudge
This skill (explicit /nudge only) manages Claude Code feature-adoption nudges sourced from the Basic Memory note main/reference/claude-code-noteworthy-features. Bare /nudge = Mode A (sync): re-read the note, filter out features already marked adopted or declined, and regenerate the tip cache…
session-reflect
This skill should be used when the user asks to 'reflect on this session', 'save insights to memory', 'capture what we learned', 'commit this to memory', 'save decisions to Basic Memory', 'write up what we did', 'preserve what we found', 'save insights from this conversation', 'save what was discovered', 'capture…
knowledge-ask
This skill should be used when the user asks 'what do I know about [topic]', 'what does Basic Memory say about [X]', 'do I have notes on [X]', 'look up [X] in my knowledge graph', 'ask memory about [X]', 'recall what we captured about [topic]', 'find notes on [topic]', 'knowledge question', 'query the knowledge…
knowledge-prime
This skill should be used when the user asks to 'prime context', 'load project knowledge', 'what do we know about this project', 'knowledge brief', 'project context', 'what packages are documented', 'show coverage for this project', 'dependency coverage report', 'which of our deps have notes', 'knowledge primer'…