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 commands/teammanagementplugin/claude-plugin/wiki-tunegit clone --depth 1 https://github.com/TeamManagementPlugin/claude-pluginWhat 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.00007 | $0.00246 |
| Opus 5 | $0.00003 | $0.00123 |
| Sonnet 5 | $0.00001 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
wiki-tune 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.
What it actually says
Wiki Tune
Customize wiki/schema.md through interactive Q&A.
Workflow
- Read the current
wiki/schema.md - If an argument specifies a section (e.g., "tags", "focus", "page-types"), focus on that section
- Ask the user questions about their domain and what the wiki should track:
- What is this project/domain about?
- What entities or concepts are most important?
- What tag categories make sense?
- What should be emphasized during ingest?
- What topics should be excluded?
- Update
wiki/schema.mdbased on the user's answers - Keep schema.md under 200 lines (auto-loaded at session start via @-ref)
Rules
- This modifies
wiki/schema.mdonly — never editCLAUDE.wiki.md(that is package-managed) - Preserve any existing content the user hasn't explicitly asked to change
- Show the user what you plan to change before writing
- If wiki/pages/ already has content, suggest tag and convention changes that are consistent with existing pages
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 · 29 lines · 7 tokens per session scan A 94ad2d4b2228
wiki-tune is a command published in the GitHub repository TeamManagementPlugin/claude-plugin (4 stars, last pushed 26d ago), licensed MIT. It adds 7 tokens to every session and 246 once invoked, about $0.0000 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 commands, from other repositories
research
Research a technical or product question.
brand-setup
Configure a new brand profile with colors, fonts, logo, visual style, platforms, and compliance rules.
save
Save this conversation as a new or existing reusable context.
graphify
Turn your vault into a clustered knowledge graph with HTML and JSON outputs.
screens
Structures product UX screen design — inventory, flow, states, and reusable briefs for external design tools — without generating pixels or UI code.
index
Command "index" from MadaraUchiha-314/the-loop, covering commands, the control plane, daemon commands, repo-scoped commands and maintenance.