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/pratiyush/llm-wiki/wiki-updategit clone --depth 1 https://github.com/Pratiyush/llm-wikiWrote 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/pratiyush/llm-wiki/wiki-update)<a href="https://agentmods.dev/commands/pratiyush/llm-wiki/wiki-update"><img src="https://agentmods.dev/badge/commands/pratiyush/llm-wiki/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.1 | $0.00000 | $0.00540 |
| Opus 5 | $0.00000 | $0.00270 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
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 6d 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
Update a single wiki page in place without running a full re-ingest.
Usage: /wiki-update [reason]
$ARGUMENTS is the path to one wiki page — typically under wiki/sources/, wiki/entities/, or wiki/concepts/.
Use this when:
- The source under
raw/changed and only one wiki page needs updating - You spotted a stale claim or broken wikilink and want to patch just that page
- You need to update
last_updatedafter a content edit - A new contradiction surfaced that should be added under
## Contradictions
Do NOT use this for bulk changes — that's what /wiki-ingest and /wiki-sync are for.
Steps:
- Read the target page using the Read tool.
- Read
wiki/index.mdto understand how this page is referenced elsewhere. - Read the source(s) listed in the frontmatter's
sources:field. - Compute the delta — what needs to change on the page? Typically one of:
- A fact or claim is now stale
- A wikilink is broken
- A contradiction needs recording
last_updatedneeds bumping- A new cross-reference should be added under
## Connections
- Edit the page with minimal targeted changes. Use the Edit tool, not Write — this is a surgical update, not a rewrite.
- Update
last_updatedin the frontmatter to today's date. - If you added/removed wikilinks, check whether backlinks on OTHER pages need updating. Report these to the user; don't update them automatically without permission.
- Append to
wiki/log.md:## [YYYY-MM-DD] update | <page-name> — <reason>
Hard rules (per .kiro/steering/page-format.md):
- Never overwrite contradictions. If new information conflicts with old, add a
## Contradictionssection, don't delete the old claim. - Keep the frontmatter schema intact.
title,type,tags,sources,last_updatedstay. - Don't mass-rewrite. If you find yourself wanting to rewrite more than 30% of the page, stop and run
/wiki-ingestagainst the underlying source instead.
After the update, summarize to the user: which page was changed, what the delta was, whether any other pages need follow-up updates, and the log entry you added.
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.
- 6d ago First seen · 42 lines · 0 tokens per session scan A 67471fa8a4db
wiki-update is a command published in the GitHub repository Pratiyush/llm-wiki (383 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 540 tokens. 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
report-schema
Print or write markdown documentation for JSON report schema.
om-incident-capture
Capture an incident from Slack channels, DMs, and threads into structured vault notes. Produces a complete incident work note with timeline, people, analysis, and brag doc entry.
adjust-length
作用: 尝试通过排版微调或受控语义改写逼近目标页数。它是专家快捷入口；普通自然语言如“把正文压到 8 页，尽量不要改语义”也应能触发同类任务。.
repair-table
作用: 针对指定表格或当前论文中的表格问题执行修复闭环。它是专家快捷入口；普通自然语言如“修 Table 2 太挤的问题”也应能触发同类任务。.
start-10-4.en
Lesson 10-4: GmailApp Email Search/Extraction → Sheet Organization!
hwpx
Safely inspect or edit an HWPX (한글 .hwpx) file using the hwpx-editing skill.