Borrowing it
Nothing to install: this file belongs to alfadur7/llm-wiki-newsroom. 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/alfadur7/llm-wiki-newsroom/main/.claude/commands/wiki-timeline.mdgit clone --depth 1 https://github.com/alfadur7/llm-wiki-newsroomWrote 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/alfadur7/llm-wiki-newsroom/wiki-timeline)<a href="https://agentmods.dev/commands/alfadur7/llm-wiki-newsroom/wiki-timeline"><img src="https://agentmods.dev/badge/commands/alfadur7/llm-wiki-newsroom/wiki-timeline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/alfadur7/llm-wiki-newsroom/wiki-timeline"><img src="https://agentmods.dev/badge/commands/alfadur7/llm-wiki-newsroom/wiki-timeline.svg" alt="Reviewed on agentmods" width="80" 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.00706 |
| Opus 5 | $0.00000 | $0.00353 |
| Sonnet 5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
wiki-timeline 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 today.
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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a chronological timeline for an entity or concept in the LLM Wiki.
Usage: /wiki-timeline <entity|concept> [year]
If $ARGUMENTS is empty: print the usage below and stop.
Usage: /wiki-timeline <entity|concept> [year]
Examples:
/wiki-timeline Meta # full chronological storyline for Meta
/wiki-timeline DeepSeek 2025 # only DeepSeek's 2025 events
/wiki-timeline OpenWeights # a concept page works too
Without a target entity/concept, backlinks cannot be collected, so it stops.
Traversal Pattern
L2-2 timeline content. The page format·authoring standard·Rubric have their SoT in layers/timeline.md; this command is the procedure that fills that standard by traversing _backlinks.json backlinks.
| Cycle | Owner |
|---|---|
| GROUND | Columnist (_backlinks.json + backlink source read) |
| APPLY | Columnist (reverse-chronological narrative authoring) |
| VERIFY₁ | Copy Editor (lint.py timeline schema) |
| VERIFY₂ | Desk (qualitative — timeline mixing·narrative flow) |
| Save | Editor-in-Chief gate + log append |
Authoring Procedure (Columnist Cycle)
- Source pool extraction =
wiki/_backlinks.jsonbacklinks ∪ the target hub's frontmattersources:. Backlinks catch only in-body[[links]]and would miss primary events linked solely via frontmatter, so the union secures them losslessly. - Sort reverse-chronologically by each source's
published:(orscraped:if absent). If a year argument is given, that year only. - Read each source → 1-2 lines of key facts. entry-date guard: the entry date must be directly backed by the source's
published(or an occurrence date stated in the body) — it cannot be later thanscraped(year typo), and when splitting one source across multiple points in time, each point must be stated in the body (otherwise demote to the hub## Timeline, no standalone timeline exposure). - History·future anchors (mature topics): include pre-ingest events·future roadmaps not in the backlinks as
- **YYYY** — [[Entity]] description/- **YYYY (planned)** —. No drops (lossless). - Flow summary (required, at top) — structure per
layers/timeline.md. - Output grouped by year (newest→oldest, reverse), with each dated item's first link =
[[source-id]](entity-first only for history anchors). - self-VERIFY₀:
python tools/lint.py timeline <slug>→ confirm→ path. - Save (when the gate is passed):
wiki/timelines/<slug>.md+log.mdappend## [YYYY-MM-DD] timeline | <entity name>.
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.
- today Changed 601845a0f36a
- 13d ago First seen · 45 lines · 0 tokens per session scan A ffd19a510199
wiki-timeline is a command published in the GitHub repository alfadur7/llm-wiki-newsroom (85 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 706 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
slm-loop
Run a task as a bounded, gate-verified loop backed by SuperLocalMemory — iterate until an independent gate passes, never on the agent's own claim.
review
When reviewing the code changes, the agent should apply general best practices to ensure high code quality. Key areas of evaluation include.
mt-onboard
Shortcut to the canonical Memtrace codebase exploration skill.
add-source
Guided add of a new source store to sources/supported-stores.json — evaluate, register, refresh, verify catalog impact.
choose-model
Compare current models across configured AI providers and produce an executable plan without running paid work. Use when the user asks which model or provider should perform a task.
checklist
Generate a custom checklist for the current feature based on user requirements.