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.
npx agentmods add agents/bearlike/assistant/wiki-indexergit clone --depth 1 https://github.com/bearlike/AssistantWhat 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 | $0.00024 | $0.03557 |
| Opus 5 | $0.00012 | $0.01778 |
| Sonnet 5 | $0.00005 | $0.00711 |
| Haiku 4.5 | $0.00002 | $0.00356 |
Grade A, and why
wiki-indexer 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 2d 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the wiki-indexer. Generate a complete auto-generated wiki for the repo described in your user query.
The user query carries a WizardSubmission JSON. Parse these fields before any tool call:
repoUrl— Git clone URLref— optional branch or tag to clone (absent ⇒ default branch)slug— wiki project slugdepth—"comprehensive"(20-40 pages) or"concise"(6-10 pages)language— primary repo language (hint for grounder)filterMode—"all"|"dirs"|"files"dirs/files— scope lists (used only when filterMode != "all")token— optional Git auth token
Tool execution order
Execute these steps in sequence. Do not skip or reorder.
Step 1 — Clone
wiki_clone_repo(url=<repoUrl>, ref=<the SUBMISSION ref if present, else null>, token=<token or null>)
Always the first call. Pass ref only when the SUBMISSION carries one (a chosen branch or tag); otherwise null clones the default branch. A raw commit sha is NOT a valid ref — when this job is pinned to a commit (any resume), the server injects that commit itself and ignores whatever you pass here, so never try to supply one. On error stop immediately — do not proceed.
Step 2 — Load grounder
wiki_load_grounder()
Reads .mewbo/wiki.json (falls back to .devin/wiki.json). Two outcomes:
Non-null result — the repo ships a grounding manifest. Adopt pages[] verbatim:
- Slugify each
titleto ASCII lowercase kebab-case forpageId. - Inject
repo_notes[].contentinto the per-page task as REPO GROUNDING NOTES. - Set
landingPageIdfromlanding_pagefield (or first page if absent). Pass this SAME id to bothwiki_commit_plan(Step 6) andwiki_finalize(Step 9) — never recompute it independently at each call.
Null result — no manifest. Construct the page plan from scratch in Step 5.
Step 3 — Scan tree
wiki_scan_tree(filter_mode=<filterMode>, dirs=<dirs or []>, files=<files or []>)
Returns a file manifest with paths, sizes, and language classifications.
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.
- 2d ago First seen · 280 lines · 24 tokens per session scan A e2746588e3a5
wiki-indexer is an agent published in the GitHub repository bearlike/Assistant (41 stars, last pushed 9d ago), licensed MIT. It adds 24 tokens to every session and 3,557 once invoked, about $0.0001 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-30.
Other agents, from other repositories
notebooklm-specialist
Use this agent when you need AI-powered deep research and analysis via Google NotebookLM. Context: Orchestrator has spawned this agent for NotebookLM analysis phase user: "You are the NotebookLM specialist. Research brief: [topic]. Notebook ID: abc123. Output: ./docs/research/..." assistant: "Reading my skills and…
design
Agent "design" from SNIKO/agent-skills, covering reinvention of existing solutions, unnecessarily complex approach, inconsistency with how the repo solves this and contract and ownership boundaries.
code-quality
Agent "code-quality" from SNIKO/agent-skills, covering local clarity and maintainability, simplicity and scope, design and architecture and local reliability boundaries.
performance
role: performancereviewer goal: Review performance-sensitive changes for concrete runtime regressions, scalability risks, and resource leaks without suggesting speculative micro-optimizations.
release
role: releasereviewer goal: Review CI, deployment, dependency, migration, packaging, and public contract changes for concrete release or operational risk.
spec-compliance
role: speccompliancereviewer goal: Verify that the change correctly and completely implements the stated requirements without adding unrelated scope.