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-ingestgit 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.00010 | $0.00490 |
| Opus 5 | $0.00005 | $0.00245 |
| Sonnet 5 | $0.00002 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
wiki-ingest 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 Ingest
Process a local file into structured wiki pages.
Input
The argument is a path to a file to ingest. The file should be in wiki/raw/ or will be referenced from there.
Workflow
- Read
CLAUDE.wiki.mdfor wiki rules and page format - Read
wiki/schema.mdfor domain focus, conventions, and the category list (## Categories) - Read
wiki/index.mdfor the current page catalog - Read the source file specified in the argument
- Discuss the key takeaways with the user — what's important, what to emphasize
- Choose the category (subdirectory under
wiki/pages/) for the page — an existing one fromwiki/schema.md, or propose a new category and confirm with the user before creating it - Create a summary page at
wiki/pages/<category>/<slug>.mdwith proper YAML frontmatter:--- title: <descriptive title> tags: [<relevant-tags>] created: <today's date> updated: <today's date> sources: [<source-filename>] --- - Check existing pages under
wiki/pages/— update any that reference the same concepts with new cross-references or revised information - Add an entry to
wiki/index.mdunder the category's heading:- [Page Title](pages/<category>/<slug>.md) — one-line description - Append to
wiki/log.md:## [<date>] ingest | <source filename>
Rules
- Accept only local file paths — do not fetch URLs
- Use wiki-root-relative markdown links for cross-references:
[Title](pages/<category>/slug.md) - Page slugs are lowercase, hyphen-separated:
authentication-flow.md; the slug lives under a category directory (pages/<category>/<slug>.md). Flatpages/<slug>.mdremains valid but prefer a category. - Tags must follow conventions in wiki/schema.md
- If the source contradicts existing wiki pages, note the contradiction explicitly in the affected pages
- Do not ingest content that duplicates CLAUDE.md or CLAUDE.tm.md
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 · 44 lines · 10 tokens per session scan A 7050d14ac007
wiki-ingest is a command published in the GitHub repository TeamManagementPlugin/claude-plugin (4 stars, last pushed 26d ago), licensed MIT. It adds 10 tokens to every session and 490 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-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.