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/index-cmd)<a href="https://agentmods.dev/commands/eduardoabreu81/livewiki/index-cmd"><img src="https://agentmods.dev/badge/commands/eduardoabreu81/livewiki/index-cmd.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.01228 |
| Opus 5 | $0.00000 | $0.00614 |
| Sonnet 5 | $0.00000 | $0.00246 |
| Haiku 4.5 | $0.00000 | $0.00123 |
Grade A, and why
index-cmd 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 7d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Indexing and ledger command
The index command reindexes a repository and synchronizes its anchor ledger while selecting human-readable, JSON, or quiet output.
When to use this page
- Run
livewiki indexto refresh extracted symbols, hashes, and anchor debt for a repository. - Combine configured ignore patterns with repeatable
--ignoreoptions for a narrower indexing walk. - Select JSON output or quiet operation when integrating the command with automation.
- Inspect ledger changes and moved pairs from the command's human-readable report.
How it fits
This module is the command-line adapter for the repository indexer and anchor-ledger services. It sits at packages/cli/src/commands/index-cmd.ts in the CLI command layer, translates Commander options into service inputs, and renders the results for a terminal or automation consumer. The excerpt does not establish the complete call graph beyond these direct service and configuration interactions.
Diagram
%% livewiki/diagrams/commands-index-cmd.mmd
Command registration and option preparation
livewiki index needs a single command surface that gathers the repository path, ignore patterns, and output preferences before invoking the indexing pipeline.
export function registerIndex(program: Command): void {
This function takes a Commander command tree and returns no value.
registerIndex registers the index command and its --ignore, --no-ledger, and --quiet options. The action resolves the repository from the current working directory and an optional --repo path, loads configuration, combines configured and command-line ignores, and then runs the indexer. The ledger runs afterward unless --no-ledger sets the derived ledger option to false.
When the ledger reports status: "aborted" the command sets process.exitCode = 1. The ledger wrote nothing in that case, so exiting zero would tell a script the wiki is reconciled when it is not.
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.
- 7d ago First seen · 89 lines · 0 tokens per session scan A 569a6f89b193
index-cmd is a command published in the GitHub repository eduardoabreu81/livewiki (0 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,228 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
why
Why the code is shaped this way — decisions, rationale, and git archaeology (question, path, or decision-health dashboard).
power-skills-rollback
Rollback a skill to a previous version.
fire-update
Check for and apply plugin updates from GitHub repository.
web-add
Fetch a web source and make its Markdown searchable in this session. Accepts a built-in alias (e.g. "react"), an HTTPS URL, or "name url" to register a custom alias.
docs-search
Search fetched Markdown by regex and pull surrounding context for the best hits. Optionally restrict to one source alias.
web-search
Search fetched web-source Markdown by regex and pull surrounding context for the best hits. Optionally restrict to one source alias.