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/baseline)<a href="https://agentmods.dev/commands/eduardoabreu81/livewiki/baseline"><img src="https://agentmods.dev/badge/commands/eduardoabreu81/livewiki/baseline/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/baseline"><img src="https://agentmods.dev/badge/commands/eduardoabreu81/livewiki/baseline.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.01010 |
| Opus 5.5 | $0.00000 | $0.00404 |
| Sonnet 5.5 | $0.00000 | $0.00202 |
| Haiku 4.5 | $0.00000 | $0.00101 |
Grade A, and why
baseline 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Baseline Management Commands
This page documents the CLI implementation for baseline lifecycle operations, covering subcommand registration, error-safe execution, and human-readable reporting.
When to use this page
- Understand how the
livewiki baselinecommand family is structured and registered. - Trace how each baseline operation (status, bootstrap, accept, move, remove, relocate) invokes the shared execution and error handling path.
- Learn how human-readable and JSON-formatted output is produced and distinguished.
- Identify the role of the status formatter in rendering repository-portable baseline health.
How it fits
A "baseline" in livewiki is an explicit, versioned record of evidence that a symbol's documented content matches its current code version. This module is the command-line user interface for baseline lifecycle operations; it sits on top of core functions exported from @livewiki/core/baseline-operations and @livewiki/core/status. The CLI reads global options (like repository root and JSON output preference), invokes the corresponding core operation function, and formats the result for display or machine consumption. This file lives in the packages/cli/src/commands/ directory alongside other command definition pages.
Diagram
%% livewiki/diagrams/commands-baseline.mmd
Command Registration
registerBaseline(program: Command): void is the exported entry point that takes a commander Command instance and attaches the entire baseline command family to it. It creates a baseline subcommand with the description "bootstrap, review, and explicitly advance versioned documentation evidence", then defines each of the six subcommands: status, bootstrap, accept, move, remove, and relocate. For each subcommand, it declares the relevant options via chained .option() calls (with .requiredOption() for mandatory inputs), and wires an action handler. The action handlers read their options — merging them with global options via command.optsWithGlobals<GlobalOptions>() — and call handle, passing the operation name, whether JSON output is requested, and an asynchronous work function that talks to a core operation module. This structure keeps commander-specific wiring at this level while delegating all real work to the core functions.
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 · 47 lines · 0 tokens per session scan A 247d28d83b49
baseline is a command published in the GitHub repository eduardoabreu81/livewiki (1 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,010 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-09-07.
Other commands, from other repositories
doc-cleanup
Identify and report obsolete or outdated documentation.
quality-gate
Run the ECC quality pipeline on demand for a file or project scope.
review
Review a skill for quality before merge.
review
Review the current diff against project memory.
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.