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/init)<a href="https://agentmods.dev/skills/odere-pro/claude-wiki-pages-plugin/init"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-wiki-pages-plugin/init.svg" alt="Measured on agentmods" 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.00077 | $0.03286 |
| Opus 5 | $0.00039 | $0.01643 |
| Sonnet 5 | $0.00015 | $0.00657 |
| Haiku 4.5 | $0.00008 | $0.00329 |
Grade A, and why
init 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 6d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM Wiki — Onboarding
Bootstrap a fresh vault/ in the user's project and hand off to the ingest
pipeline. The skill is idempotent and self-repairing: it always persists
the chosen vault path, creates the vault directory if it is missing, and
fills in any missing required files or subdirectories from the plugin's
reference scaffold without overwriting user content. Running it twice on a
healthy vault is a no-op.
This skill owns initialization. It does not ingest, lint, or query — those
roles belong to /claude-wiki-pages:ingest,
/claude-wiki-pages:lint, and /claude-wiki-pages:query.
When to invoke
- The user has installed the plugin and asks how to start.
- No
vault/directory exists in the user's project. - The vault directory exists but is empty or missing required files / folders.
- The user explicitly asks for a new vault or wants to reset to a known-good scaffold.
Safe to invoke even when a populated vault already exists — the skill detects that case, reports the current state, ensures settings are persisted, and exits without overwriting anything.
Reading contract
Sealed inputs this skill may read:
- The plugin's own
${CLAUDE_PLUGIN_ROOT}/skills/init/template/tree — the reference scaffold used as the copy source. This is always the plugin cache path, never a project-local path (even when the user's chosen vault happens to bedocs/vault). - The plugin's
${CLAUDE_PLUGIN_ROOT}/skills/init/template/CLAUDE.md— the authoritative schema. - The user's project root — to determine the target install path and detect a prior install.
This skill MUST NOT read raw/ or wiki/ content from any other source.
Writing contract
Two write targets, both scoped to the user's project:
<project>/<vault>/— the scaffold tree. Only missing files and directories are written; existing user content is never overwritten.<project>/.claude/claude-wiki-pages/settings.json— written viascripts/set-vault.shso the chosen vault path persists across sessions.
What ships with it
17 files 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.
- template/_inbox/.gitkeep 0 B
- template/_templates/concept.md 654 B
- template/_templates/entity.md 572 B
- template/_templates/index.md 789 B
- template/_templates/project.md 776 B
- template/_templates/source.md 983 B
- template/_templates/synthesis.md 246 B
- template/_templates/topic.md 721 B
- template/.gitignore 154 B
- template/CLAUDE.md 48 KB
- template/raw/.gitkeep 0 B
- template/raw/assets/.gitkeep 0 B
- template/raw/sample-source.md 2.4 KB
- template/wiki/_sources/.gitkeep 0 B
- template/wiki/_synthesis/.gitkeep 0 B
- template/wiki/index.md 701 B
- template/wiki/log.md 403 B
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.
- 6d ago First seen · 244 lines · 77 tokens per session scan A b5ed3ddfe7aa
init is a skill published in the GitHub repository odere-pro/claude-wiki-pages-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 3,286 once invoked, about $0.0004 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…
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'…
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…