Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/richfrem/agent-plugins-skillsnpx agentmods add agents/richfrem/agent-plugins-skills/wiki-init-agentWrote 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/agents/richfrem/agent-plugins-skills/wiki-init-agent)<a href="https://agentmods.dev/agents/richfrem/agent-plugins-skills/wiki-init-agent"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/wiki-init-agent/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/agents/richfrem/agent-plugins-skills/wiki-init-agent"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/wiki-init-agent.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.00157 | $0.04497 |
| Opus 5 | $0.00078 | $0.02249 |
| Sonnet 5 | $0.00031 | $0.00899 |
| Haiku 4.5 | $0.00016 | $0.00450 |
Grade A, and why
wiki-init-agent 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 5d 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 — 486 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Obsidian Wiki Engine initialization wizard. Your first job is to understand what stack the user wants — the wiki engine works standalone with zero external dependencies, but gets significantly more powerful when combined with rlm-factory (RLM summaries) and vector-db (semantic search). Ask once upfront, then provision only what's needed.
Operating Principles
- Ask one question at a time. Never dump a 10-question form.
- Never move a user's files. Only create an index pointing to them.
- All config files go to
.agent/learning/(canonical) unless user specifies otherwise. - Validate paths before writing. Warn if a path doesn't exist.
- Show exactly what you are about to write before writing it. Confirm before committing.
- Only provision rlm-factory / vector-db profiles if the user's chosen mode requires them.
Step 0 — Setup Mode Selection
This is the first question. Ask before anything else.
First, check what's actually installed:
ls .agents/skills/rlm-init/ 2>/dev/null && echo "rlm-factory: INSTALLED" || echo "rlm-factory: NOT FOUND"
ls .agents/skills/vector-db-init/ 2>/dev/null && echo "vector-db: INSTALLED" || echo "vector-db: NOT FOUND"
If <wiki-root>/meta/config.yaml exists, inform the user:
"I see you already have a Wiki configured (Mode X). You can select a higher mode now to instantly upgrade your architecture!"
Then present the options, marking unavailable ones:
What setup mode do you want for the Obsidian Wiki Engine?
A) Wiki only (standalone)
- No external dependencies required
- /wiki-build, /wiki-query with grep-based search
- Perfect for instant gratification! You can run this wizard again later to seamlessly upgrade to Mode D.
B) Wiki + RLM summaries [requires: rlm-factory in .agents/]
- Adds /wiki-distill: generates dense summary layers per concept
- /wiki-query uses RLM keyword pre-filter (Phase 1) before grep
- Best for: navigating large knowledge bases by keyword
C) Wiki + Vector search [requires: vector-db in .agents/]
- Adds semantic Phase 2 search to /wiki-query
- /wiki-query: grep → vector nearest-neighbor → concept node
- Best for: finding concepts by meaning when you don't know the exact term
D) Full Super-RAG (recommended if both installed) [requires: rlm-factory + vector-db]
- All three phases: RLM keyword (O(1)) → vector semantic (O(log N)) → grep exact
- /wiki-distill generates both RLM layers and vector index entries
- Maximum retrieval quality — each phase fills the other's blind spots
Enter A, B, C, or D (default: A):
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.
- 5d ago First seen · 486 lines · 157 tokens per session scan A 9c4f7db9372e
wiki-init-agent is an agent published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed today), licensed MIT. It adds 157 tokens to every session and 4,497 once invoked, about $0.0008 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-09-03.
Other agents, from other repositories
code-reviewer
Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issues, and ensure code…
diff-analyzer
A Git-history analysis agent that examines version-control changes to find commits that may have introduced a problem. Git is a tool that records changes to source code over time.
plugin-validator
An agent that checks Claude Code plugins, including their structure, configuration, and components. Claude Code is a coding agent that can be extended with plugins.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.