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.
git clone --depth 1 https://github.com/eduardoabreu81/livewikiWrote 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/eduardoabreu81/livewiki/status)<a href="https://agentmods.dev/commands/eduardoabreu81/livewiki/status"><img src="https://agentmods.dev/badge/commands/eduardoabreu81/livewiki/status/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/eduardoabreu81/livewiki/status"><img src="https://agentmods.dev/badge/commands/eduardoabreu81/livewiki/status.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.00707 |
| Opus 5.5 | $0.00000 | $0.00283 |
| Sonnet 5.5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
status 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 1mo 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
livewiki status command
This page documents the CLI command that reports the current health of a livewiki index.
When to use this page
- Run
livewiki statusto see whatrunStatusandformatStatusHumanemit and how--jsonand--topreshape that report. - Inspect
registerStatusto understand how--diffswitches the handler fromrunStatusinto thepreviewWorkingTreeDebtpath. - Review how the command degrades when the working tree is not a git repository.
- Trace the command-level error handling that funnels unexpected throws into a single non-zero exit code.
How it fits
packages/cli/src/commands/status.ts is one of the subcommand registrations wired into the top-level livewiki Commander program. It delegates the actual report and diff work to two sibling modules in @livewiki/core: status (which produces the index report and a human formatter) and diff-preview (which produces the read-only working-tree diff preview and its human formatter). The file itself contains no scanning or git logic — it only adapts CLI flags into the inputs those core helpers expect.
Diagram
%% livewiki/diagrams/commands-status.mmd
Status command registration
The single responsibility of registerStatus is to attach a status subcommand to the Commander program and to translate its flags into the arguments the core helpers understand.
export function registerStatus(program: Command): void
registerStatus takes the shared Command instance and returns nothing; it registers the subcommand as a side effect.
Inside the handler, the file first resolves the repository root (path.resolve(process.cwd(), opts.repo ?? ".")) and parses opts.top into an integer defaulting to 10, then branches on --diff:
- Without
--diff— callsrunStatus(repoRoot, { topN })to produce the index report. The result is either serialized to stdout as{ ok: true, ...report }JSON (when--jsonis set) or rendered throughformatStatusHuman. - With
--diff— callspreviewWorkingTreeDebt(repoRoot)for a read-only pre-commit preview of the anchors the uncommitted working-tree diff would invalidate. The result is again emitted either as JSON or viaformatDiffPreviewHuman.
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.
- 1mo ago First seen · 46 lines · 0 tokens per session scan A 97659b9edfe6
status is a command published in the GitHub repository eduardoabreu81/livewiki (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 707 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-31.
Other commands, from other repositories
web-search
Search fetched web-source Markdown by regex and pull surrounding context for the best hits. Optionally restrict to one source alias.
docs-refresh
Re-fetch a cached source, ignoring the 7-day cache. Use when upstream content has changed.
fire-resurrect
Autonomous Resurrection Mode — reverse-engineer intent from messy code, then rebuild clean from scratch.
fire-debug
Systematic debugging with persistent state, skills library integration, and WARRIOR validation.
fire-reflect
After any failure (debug resolution, test failure, approach rotation, stalled loop), capture what was tried, why it failed, and what actually worked as a persistent reflection. Future sessions search these before investigating.
fire-verify-uat
Conversational User Acceptance Testing with automatic parallel diagnosis on failures.