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-syncgit 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-sync)<a href="https://agentmods.dev/commands/pratiyush/llm-wiki/wiki-sync"><img src="https://agentmods.dev/badge/commands/pratiyush/llm-wiki/wiki-sync.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.00000 | $0.00603 |
| Opus 5 | $0.00000 | $0.00302 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
wiki-sync 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.
What it actually says
Sync Claude Code (and Codex CLI) session transcripts into the llmwiki, then ingest the new ones into wiki/.
Usage: /wiki-sync [project-substring]
Steps (run in this order, report progress to the user):
-
Convert new sessions to markdown by running:
python3 -m llmwiki sync $ARGUMENTSCapture the summary line (
N converted, M unchanged, K live, J filtered, X errors). -
If
N == 0: report "wiki is already up to date" and continue to step 6 (pending-prompt scan). Don't run ingest. -
If
N > 0: for each newly written markdown file underraw/sessions/, follow the Ingest Workflow fromCLAUDE.md. Process one project at a time. If there are more than 20 new files total, ask the user whether to process them all or a subset first. -
Append to
wiki/log.md:## [YYYY-MM-DD] sync | <N> sessions across <M> projects -
Report to the user:
- How many sessions were converted
- Which projects got updated
- Which wiki pages were created or updated
- Any contradictions flagged under
## Contradictionson wiki pages
-
Complete any pending agent-delegate syntheses (#316) — the
agentsynthesis backend writes pending prompts to.llmwiki-pending-prompts/<uuid>.mdthat need you (the agent) to finalise. Run:python3 -m llmwiki synthesize --list-pendingIf the output is "No pending prompts": skip to step 7.
Otherwise — for each pending prompt:
a. Read
.llmwiki-pending-prompts/<uuid>.md— it contains the rendered prompt (body + frontmatter) that the pipeline already filled in.b. Synthesize the wiki page body by following the prompt instructions. Emit the
<!-- suggested-tags: ... -->comment as the first line per the prompt.c. Write the synthesized body to a scratch file, then finalise:
python3 -m llmwiki synthesize --complete <uuid> --page wiki/sources/<project>/<date>-<slug>.md --body /tmp/synth-<uuid>.mdd. The CLI verifies the uuid matches the page's sentinel, rewrites the placeholder in place, and deletes
.llmwiki-pending-prompts/<uuid>.md.Process all pending prompts serially — the agent is single-conversation.
-
Done. Run
/wiki-buildif the caller asked for fresh HTML.
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 · 53 lines · 0 tokens per session scan A fff3bcd3109b
wiki-sync 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 603 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
ppl
Add or update a person you interacts with in the wiki (wiki/entities/people/). Usage: /ppl . Also: /ppl list, /ppl lookup , /ppl edit .
update-memory
Check and update CLAUDE.md memory based on changes to skills, commands, agents, and hooks.
wiki-query
Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.
wiki-digest
Generate a daily or weekly digest of wiki changes — new sources, pages, insights, and gaps.
kiro-steering-custom
Command "kiro-steering-custom" from gotalab/cc-sdd, covering kiro custom steering creation, workflow, available templates, steering principles and tool guidance.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.