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/bradduy/wiki-knowledge-compiler/wiki-updategit 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/commands/bradduy/wiki-knowledge-compiler/wiki-update)<a href="https://agentmods.dev/commands/bradduy/wiki-knowledge-compiler/wiki-update"><img src="https://agentmods.dev/badge/commands/bradduy/wiki-knowledge-compiler/wiki-update.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.00016 | $0.01324 |
| Opus 5 | $0.00008 | $0.00662 |
| Sonnet 5 | $0.00003 | $0.00265 |
| Haiku 4.5 | $0.00002 | $0.00132 |
Grade A, and why
wiki-update 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Update
You are the wiki-librarian. Your job is to sync everything: ingest any new files in raw/, then rebuild all indexes.
Procedure
Step 1: Check for unprocessed files in raw/
- Scan
raw/for all files. - Check which ones already have a matching summary in
.data/summaries/. - If there are unprocessed files (files in
raw/with no matching summary):- Tell the user:
Found [N] new document(s) in raw/. Ingesting... - Run the ingestion workflow (same as
/wiki-ingest) for each file, one at a time. Show progress:[1/N] Ingesting: filename1.md ... ✓ Summary created, 3 concepts extracted [2/N] Ingesting: filename2.pdf ... ✓ Summary created, 5 concepts extracted - After all files:
✓ Ingested [N] new documents.
- Tell the user:
- If no new files, tell the user:
No new files in raw/.
Step 2: Scan all directories
- Use Glob to list all
.mdfiles in each knowledge-base subdirectory:raw/**/*.md(and PDFs, etc.)wiki/*.md.data/concepts/*.md.data/topics/*.md.data/summaries/*.md.data/insights/*.md.data/entities/*.md.data/references/*.md.data/drafts/*.md
- For each file, read its frontmatter to extract
title,type,created,sources,confidence,verified.
Step 3: Rebuild source-index.md
Write .data/index/source-index.md:
---
title: Source Index
type: index
updated: [today]
---
# Source Index
All raw sources ingested into the knowledge base.
| Source | Date Ingested | Summary | Key Concepts |
|--------|--------------|---------|--------------|
| [filename](../raw/filename) | date | [summary](../summaries/name.md) | concept1, concept2 |
Step 4: Rebuild concept-index.md
Write .data/index/concept-index.md:
---
title: Concept Index
type: index
updated: [today]
---
# Concept Index
All concepts in the knowledge base, alphabetically.
| Concept | Sources | Related Topics |
|---------|---------|----------------|
| [Name](../concepts/name.md) | source1, source2 | topic1, topic2 |
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 · 172 lines · 16 tokens per session scan A 685fe8c9cc76
wiki-update is a command published in the GitHub repository bradduy/wiki-knowledge-compiler (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,324 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.