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/TeamManagementPlugin/claude-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/teammanagementplugin/claude-plugin/wiki-lint)<a href="https://agentmods.dev/commands/teammanagementplugin/claude-plugin/wiki-lint"><img src="https://agentmods.dev/badge/commands/teammanagementplugin/claude-plugin/wiki-lint/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/teammanagementplugin/claude-plugin/wiki-lint"><img src="https://agentmods.dev/badge/commands/teammanagementplugin/claude-plugin/wiki-lint.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.00014 | $0.00736 |
| Opus 5.5 | $0.00006 | $0.00294 |
| Sonnet 5.5 | $0.00003 | $0.00147 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade A, and why
wiki-lint 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Lint
Audit wiki/pages/ for structural and content quality issues.
Scale Check
First, count the number of .md files in wiki/pages/:
find wiki/pages -name "*.md" | wc -l
If more than 50 pages: Delegate this entire lint operation to the Agent tool (subagent_type: "general-purpose") with the prompt below. This prevents context overflow from reading all pages inline.
If 50 or fewer pages: Perform the lint inline.
Checks
Pages may be nested in category subdirectories (wiki/pages/<category>/<slug>.md) or flat (wiki/pages/<slug>.md, legacy). find wiki/pages -name "*.md" already recurses. Normalize every page and link target to its wiki-root-relative path (e.g. pages/<category>/<slug>.md) before comparing — links are written relative to the wiki root, not to the page's own directory.
- Orphan pages — files under wiki/pages/ (any depth) not listed in wiki/index.md (compare normalized wiki-root-relative paths, not bare slugs)
- Missing pages — entries in wiki/index.md pointing to files that don't exist
- Broken internal links — markdown links in pages pointing to non-existent pages; resolve
pages/...link targets from the wiki root - Missing frontmatter — pages lacking required YAML fields (title, tags, created, sources)
- Stale content — pages whose
updateddate is more than 90 days old (flag for review) - Tag inconsistency — tags used in pages but not defined in schema.md conventions
- Index completeness — pages that exist but have no description in the index
- Uncategorized pages (info) — pages sitting flat in wiki/pages/ rather than under a category; valid but suggest moving into a category
- Category consistency (info) — category directories under wiki/pages/ not listed in schema.md
## Categories, or schema categories with no pages yet
Note: the same slug under two different categories (pages/api/auth.md and pages/security/auth.md) is allowed — pages are addressed by full path. Do not report a duplicate-basename collision as an error; at most note it as info if it looks unintentional.
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 · 64 lines · 14 tokens per session scan A 201a99976974
wiki-lint is a command published in the GitHub repository TeamManagementPlugin/claude-plugin (6 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 736 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
dream
Overnight autoresearch + maintainer sweep that surfaces a MORNING REPORT — suggested changes, issues raised with fixes, and kept improvements. Shadow-first; never auto-pushes. Runs on-demand or scheduled for off-hours.
maintain
Run automated maintenance — seeker finds bugs from pod logs and raises GitHub issues, fixer picks them up and creates PRs. Can run as a one-shot or scheduled via /schedule.
debloat
Retroactive whole-repo bloat removal (spec H-2ii). Scores an existing repo on the deterministic bloat axes, writes BLOAT-REPORT.md, and — only behind a passing test-suite safety oracle — proposes gated refactor waves as a PR. The zero-risk adoption hook.
p6-exploratory
Conducts unstructured, experience-based tests that automated tests and defined test cases do not cover. The goal is to find unexpected behaviours, usability issues, and hidden bugs that remain invisible in structured testing.
p8-ops
Analyses production errors and performance issues, evaluates incidents, and initiates countermeasures. Called reactively for specific incidents or proactively for regular operational reviews.
p6-bugfix
Fixes bugs and vulnerabilities found during the QA phase (functional tests, exploratory tests, accessibility check, security audit, pentest). Each fix is secured by a regression test.