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/export)<a href="https://agentmods.dev/commands/eduardoabreu81/livewiki/export"><img src="https://agentmods.dev/badge/commands/eduardoabreu81/livewiki/export/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/export"><img src="https://agentmods.dev/badge/commands/eduardoabreu81/livewiki/export.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.02038 |
| Opus 5.5 | $0.00000 | $0.00815 |
| Sonnet 5.5 | $0.00000 | $0.00408 |
| Haiku 4.5 | $0.00000 | $0.00204 |
Grade A, and why
export 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Export command
The livewiki export command turns the project's curated wiki into a deliverable artifact on disk: either a flattened snapshot under .livewiki/export/<target>/ (for generic, github-wiki, and gitlab-wiki targets) or a synthesized repository-root README.md (for the readme target).
When to use this page
- Register or extend the
exportsubcommand on the Commander program. - Trace how a thrown
ExportError(or any unexpected error) is converted into the structured JSON payload the CLI contract promises. - Reason about the dry-run versus write semantics for the
readmetarget and how--yesflips them. - Understand why
--pushis rejected up front in this lot and where the exit code is decided.
How it fits
packages/cli/src/commands/export.ts is part of the @livewiki/cli package and lives under src/commands/. It defines the export <target> subcommand by calling registerExport(program) from the top-level CLI wiring in packages/cli/src/cli.ts. The flatten/copy pipeline (for generic, github-wiki, gitlab-wiki) and the validateTarget guard both come from @livewiki/core/export; the README synthesis path reuses exportReadme and the ReadmeExportResult contract from @livewiki/core/readme-export. Repo-root resolution (resolveRepoRoot) is shared with the rest of the CLI. This file is the glue that decides which core entry point to invoke, normalizes errors into a stable result shape, and renders either JSON or human output before setting process.exitCode.
Diagram
%% livewiki/diagrams/commands-export.mmd
Command registration and dispatch
The entry point exposed by this file is the registration call that wires livewiki export <target> onto the root Commander program.
export function registerExport(program: Command): void {
registerExport takes the shared Commander program and returns nothing; it attaches the export <target> subcommand, declares the --force, --yes, and --push flags, and installs the async action handler that resolves options, picks the dispatch branch, and emits the final result. Inside the action handler it merges global options (optsWithGlobals), resolves the repository root via resolveRepoRoot(opts.repo), and computes an absolute path before doing anything else — that absolute root is what every downstream core call sees.
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 · 103 lines · 0 tokens per session scan A 670d53f567c2
export 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,038 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
output
Generate output artifacts from active wiki content — summaries, reports, study guides, slide outlines, timelines, glossaries, comparisons. Outputs are filed back into the wiki.
export-okf
Export ArcKit project artifacts as an Open Knowledge Format bundle without changing source ARC files.
ingest
Batch-convert all supported files in a folder to Markdown.
doc-review
Review documentation for quality, accuracy, and completeness.
performance-review
Use this command to analyze content performance data and generate a prioritized queue of content tasks.
research-gaps
Identify content gaps where competitors rank but you don't.