Borrowing it
Nothing to install: this file belongs to Pratiyush/llm-wiki. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Pratiyush/llm-wiki/master/.claude/commands/wiki-reflect.mdgit 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-reflect)<a href="https://agentmods.dev/commands/pratiyush/llm-wiki/wiki-reflect"><img src="https://agentmods.dev/badge/commands/pratiyush/llm-wiki/wiki-reflect.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.00709 |
| Opus 5 | $0.00000 | $0.00354 |
| Sonnet 5 | $0.00000 | $0.00142 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
wiki-reflect 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 8d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run a self-reflection pass over the whole wiki — look for patterns, gaps, and improvement opportunities.
Usage: /wiki-reflect [focus-area]
$ARGUMENTS is an optional focus hint: patterns, gaps, quality, contradictions, or omit for a general pass.
Unlike /wiki-lint (which finds structural issues) or /wiki-query (which answers one question), /wiki-reflect asks the higher-order question: what is this wiki trying to say, and what's missing?
Steps
-
Read
wiki/index.mdandwiki/overview.mdto get the current synthesis. -
Read every page under
wiki/sources/,wiki/entities/, andwiki/concepts/— or a representative sample if there are more than 50 pages. -
Look for:
- Recurring themes that span multiple sources — candidates for new concept pages
- Implicit comparisons where two entities or concepts keep appearing together — candidates for
wiki/comparisons/pages - Unanswered questions mentioned in multiple sources — candidates for
wiki/questions/pages - Evolution over time — how has the user's thinking on a concept changed?
- Contradiction clusters — pages that disagree on the same point
- Orphan themes — interesting ideas mentioned once then never again
- Missing entities — people, tools, or projects mentioned in 3+ sources without their own page
-
Synthesise a 3-5 paragraph reflection structured as:
- What the wiki knows well — the most-covered topics, the strongest signal
- What the wiki is missing — gaps that reflection surfaced
- Suggested next actions — new pages, new queries, or new sources to ingest
-
Ask the user whether to:
- Save the reflection as
wiki/syntheses/reflection-<YYYY-MM-DD>.md - Open GitHub issues for any "new page" suggestions
- Schedule a
/wiki-ingestof any missing sources the reflection identified
- Save the reflection as
-
Append to
wiki/log.md:## [YYYY-MM-DD] reflect | <short summary of findings>
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.
- 8d ago First seen · 54 lines · 0 tokens per session scan A 23f09ea6bfd3
wiki-reflect is a command published in the GitHub repository Pratiyush/llm-wiki (385 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 709 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
prompt-pilot
Rewrite a rough prompt into a precise, context-enriched prompt (read-only — never implements the task).
sdd-apply
Implement SDD tasks — writes code following specs and design.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
kb-ingest
Ingest external material into Sources/ inside the bound project KB, then update registry, index, and daily note as needed.
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
security-flow-inspect-and-test
Phase 5 Inspect and Test of security-flow.