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/batch)<a href="https://agentmods.dev/commands/eduardoabreu81/livewiki/batch"><img src="https://agentmods.dev/badge/commands/eduardoabreu81/livewiki/batch/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/batch"><img src="https://agentmods.dev/badge/commands/eduardoabreu81/livewiki/batch.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.02572 |
| Opus 5.5 | $0.00000 | $0.01029 |
| Sonnet 5.5 | $0.00000 | $0.00514 |
| Haiku 4.5 | $0.00000 | $0.00257 |
Grade A, and why
batch 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Batch CLI command: registration and human-readable reporting
This page documents how the livewiki batch command is registered with the Commander CLI framework and how it formats batch run reports for human consumption.
When to use this page
- Understand how the
livewiki batchcommand dispatches its subcommands (status,resume,list, and--only). - Learn how token, USD, failure, and recovery-tier information is formatted into the human-readable output for batch status and result reports.
- See how exit codes are derived from run status for non-JSON output.
- Trace how failed stage-4 tasks surface their per-attempt diagnostic history in status reports.
How it fits
This file lives in the CLI package (packages/cli/src/commands/), which is the user-facing command layer of livewiki. It depends on core batch logic imported from @livewiki/core/batch (specifically runBatch, resumeBatch, runOnly) and @livewiki/core/batch-status (buildStatusReport, listRuns). The file's role is to wire a Commander subcommand to those core functions and to translate their structured results into either JSON (via the shared emit helper) or human-readable text. It also sets the process exit code based on run status, except when JSON output is requested, in which case the exit code is always 0.
The mechanics in this file are purely about CLI orchestration and presentation: it validates user input, calls the core functions, formats the returned data, and signals the outcome through the exit code.
Diagram
%% livewiki/diagrams/commands-batch.mmd
Subcommand dispatch
The registerBatch function is the single entry point that registers the batch command on the provided Commander program. It takes a Command instance and returns void.
export function registerBatch(program: Command): void {
The function receives the Commander program and registers a batch command on it. It declares three options: --only <target> to re-run a single task, --no-refine to skip LLM refinement (Commander maps this to refine === false), and --concurrency <n> to set the stage-4 worker pool size (an integer 1..16). The action handler then resolves the repository root, parses the positional arguments, and dispatches based on the first argument.
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 · 153 lines · 0 tokens per session scan A 1cbbcb658df5
batch is a command published in the GitHub repository eduardoabreu81/livewiki (1 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,572 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
plan
Create a phased implementation plan before writing any code.
megacave
Activate megacave mode (caveman in Classical Chinese).
help
Quick reference for all Attune commands.
web-search
Search fetched web-source Markdown by regex and pull surrounding context for the best hits. Optionally restrict to one source alias.
fire-todos
Capture, list, and manage todos during work sessions.
docs-refresh
Re-fetch a cached source, ignoring the 7-day cache. Use when upstream content has changed.