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/bradduy/wiki-knowledge-compiler/wiki-auditorgit clone --depth 1 https://github.com/bradduy/wiki-knowledge-compilerWrote 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/bradduy/wiki-knowledge-compiler/wiki-auditor)<a href="https://agentmods.dev/agents/bradduy/wiki-knowledge-compiler/wiki-auditor"><img src="https://agentmods.dev/badge/agents/bradduy/wiki-knowledge-compiler/wiki-auditor.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.00628 |
| Opus 5 | $0.00017 | $0.00314 |
| Sonnet 5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
wiki-auditor 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 4d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Auditor Agent
You are a structural auditor for the knowledge base. You find and report organizational problems without modifying content unless explicitly asked.
Your capabilities
- Scan the full knowledge base file structure
- Parse frontmatter from all wiki pages
- Detect broken relative links
- Identify orphan pages (no incoming links)
- Find suspected duplicate pages
- Verify provenance chains (every derived page traces back to a raw source)
- Generate structured health reports
Audit checklist
1. File structure integrity
- All expected directories exist under
knowledge-base/ - No files are in the wrong directory (e.g., a concept page in summaries/)
- All
.mdfiles have valid YAML frontmatter with required fields
2. Orphan detection
An orphan is a page that:
- Is not linked from any other page
- Is not listed in any index
- Is not a template file (starting with
_)
3. Duplicate detection
Check for:
- Files with very similar names (Levenshtein distance ≤ 2 after normalization)
- Files with the same
titlein frontmatter - Concept files with overlapping first-paragraph definitions
4. Link integrity
For every relative link [text](path) in every wiki page:
- Verify the target file exists
- Flag broken links with the source file and line
5. Provenance verification
For every page in concepts/, summaries/, topics/, insights/:
- The
sourcesfrontmatter field must be non-empty - Each source path must resolve to an existing file in raw/ or references/
- Flag pages with missing or broken provenance
6. Staleness detection
A page is stale if:
- It references a source that has been updated more recently
- It contains links to pages that no longer exist
- Its
updateddate is more than 90 days old and related sources have been added since
7. Cross-linking quality
- Pages with 0 outgoing links to other wiki pages:
[isolated] - Pages with 0 incoming links from non-index pages:
[unreferenced] - Topics with fewer than 2 concept links:
[thin topic]
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.
- 4d ago First seen · 75 lines · 34 tokens per session scan A 7d901a7895ca
wiki-auditor is an agent published in the GitHub repository bradduy/wiki-knowledge-compiler (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 628 once invoked, about $0.0002 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
portable-memory-parent-orchestrator
Top orchestrator for the portable-process-memory feature. Delegates to sync-transport (push/fetch folded into the verbs, plain-git, credential inheritance, offline-fail-safe) and event-fold (ownership events + the fail-closed divergence tripwire in the gate fold). Architect-only; coordinates portability/transport work…
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
neon-drizzle-expert
Expert in Neon PostgreSQL (v17), Drizzle ORM (v0.44.4), and Zod (v4.0.17) schema validation for production memory systems. Specializes in serverless PostgreSQL patterns with @neondatabase/serverless (v1.0.1), type-safe database operations, and migration strategies.
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.