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.
git clone --depth 1 https://github.com/odere-pro/claude-wiki-pages-pluginWrote 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/commands/odere-pro/claude-wiki-pages-plugin/onboarding)<a href="https://agentmods.dev/commands/odere-pro/claude-wiki-pages-plugin/onboarding"><img src="https://agentmods.dev/badge/commands/odere-pro/claude-wiki-pages-plugin/onboarding/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/commands/odere-pro/claude-wiki-pages-plugin/onboarding"><img src="https://agentmods.dev/badge/commands/odere-pro/claude-wiki-pages-plugin/onboarding.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.00032 | $0.00409 |
| Opus 5.5 | $0.00013 | $0.00164 |
| Sonnet 5.5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
onboarding 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 1mo 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.
What it actually says
/claude-wiki-pages:onboarding
The friendliest way in. Hands control to the claude-wiki-pages-onboarding-agent,
which walks you from "just installed" to "I got a cited answer from my own wiki"
one step at a time — health check, scaffold, add a source, ingest (with automatic
git-checkpointed self-heal), ask a question.
What this command does
- Probe state. Resolve the vault and check what already exists, so it resumes rather than restarts.
- Delegate to the onboarding agent via the
Tasktool, passing$ARGUMENTS(e.g. a topic you care about, or "use the sample source"). - Surface each step's result with a plain-language explanation of what just happened and what is next.
When to use this command
- You just installed the plugin and want a guided start.
- You are unsure which skill or command to run first.
- You want to see the whole loop — scaffold → ingest → query — once, end to end.
For the unguided one-verb entry, use /claude-wiki-pages:wiki. For an environment health check, use /claude-wiki-pages:doctor.
Invocation
Task → claude-wiki-pages-onboarding-agent
prompt: $ARGUMENTS
context: vault path, schema version (if present), raw/ count
Specification anchor
Contracts: docs/architecture.md (commands & claude-wiki-pages-onboarding-agent).
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.
- 1mo ago First seen · 39 lines · 32 tokens per session scan A dbf1afc19795
onboarding is a command published in the GitHub repository odere-pro/claude-wiki-pages-plugin (1 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 409 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
scout-work
Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).
tidy
Consistency check for non-code repos with INDEX.md hierarchy. Verifies INDEX.md accuracy, MEMORY.md references, orphaned files, stale dates, and WAITING markers.
pm-learn
Auto-extract repeatable patterns, decisions, and cost outliers from the current session and append to .great-pm/lessons.md. Promotes ≥3-occurrence patterns to /.great-pm/decisions.md. Runs continuous-learner.
pm-save
Extract lessons from this session and save them to .great-pm/lessons.md. Optional cross-project promotion to /.great-pm/decisions.md for patterns seen 3+ times (proposed, never auto-promoted).
pm-resume
Pick up where you left off. Reads .great-pm/HANDOFF.md (auto-saved by the PreCompact hook) and orients you with the next concrete step.