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.
npx agentmods add commands/eduardoabreu81/livewiki/viewgit 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/view)<a href="https://agentmods.dev/commands/eduardoabreu81/livewiki/view"><img src="https://agentmods.dev/badge/commands/eduardoabreu81/livewiki/view.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 | $0.00000 | $0.01544 |
| Opus 5 | $0.00000 | $0.00772 |
| Sonnet 5 | $0.00000 | $0.00309 |
| Haiku 4.5 | $0.00000 | $0.00154 |
Grade A, and why
view 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 3d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
View command
The livewiki view CLI command builds a self-contained static site from the canonical livewiki/ wiki and opens it in a browser.
When to use this page
- Wire the
viewsubcommand onto the rootcommanderprogram when bootstrapping the CLI. - Trace how option parsing, build invocation, and post-build browser launch flow from one entry point.
- Debug the cross-platform browser-open behaviour or the fail-open handling around missing openers.
- Extend the view pipeline (new flags, new templates) by following the existing option/action split.
How it fits
packages/cli/src/commands/view.ts lives under packages/cli/src/commands/, the directory that holds every subcommand the root CLI registers. The module imports Command from commander, spawn and node:path from Node, the core view engine from @livewiki/core/view, configuration loading from @livewiki/core/config, and the repo-root resolver plus human/JSON emitters from sibling CLI files. Its role is narrow: it does not build the site itself — it parses flags, validates the few inputs it owns, delegates to buildSite from core, then decides whether to launch a browser. Two symbols do all of that work: registerView attaches the subcommand, and openBrowser is the small helper used at the end of a successful run.
Diagram
%% livewiki/diagrams/commands-view.mmd
Subcommand registration and option parsing
registerView is the single entry point the root CLI calls to mount the subcommand; the file has no other exported symbol. Its job is to declare the view verb, attach every flag it understands, and run the build when the user invokes it.
export function registerView(program: Command): void {
The signature takes the root commander.Command and returns nothing; the command is attached as a side effect of the .command("view")...action(...) chain.
The action body proceeds in stages. First, it re-reads the merged options via command.optsWithGlobals<ViewCliOptions>() so that global flags like --json are visible, and it resolves the repository root through resolveRepoRoot from the parent CLI module.
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.
- 3d ago First seen · 72 lines · 0 tokens per session scan A be6a4e14b833
view is a command published in the GitHub repository eduardoabreu81/livewiki (0 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,544 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
capture-answer
Ingests an expert's answers to an L2 questionnaire in the abapwiki knowledge base: transforms the answers (filled in the interviews/ file or given verbally) into a canonical citable expert-answer (slices/ /inputs/expert-answers/), moves gaps to 'answered' and closes the questions. Use this skill when the owner/expert…
ingest-l1
L1 analysis loop for the abapwiki knowledge base: for each batch it launches the abap-analyzer sub-agent in parallel, then the adversarial judge abap-deepcheck (separate session), applies only the analyses that pass the fail-closed gate, and commits. Resumes exactly after an interruption. Use this skill to document…
research-l2
Executes Phases 1-3 of the L2 process of the abapwiki knowledge base on a slice: launches the abap-functional-researcher sub-agent (gap discovery + multi-source auto-research: wiki -> raw/docs -> MCP abap-fs on the system read-only -> standard knowledge), ingests gaps and evidence, and generates questionnaires for…
slice-init
Creates an L2 slice in the abapwiki knowledge base: a business process on which to build functional documentation. Writes the manifest (curated anchors + mandatory real owner) and derives the membership from the dependency graph (BFS hop<=2). Use this skill to start the L2 process on a custom domain. Does not promote…
ingest-l0
L0 bootstrap of the abapwiki knowledge base: creates stubs for all custom objects from the TADIR. Use this skill to initialize the repo from scratch or to ingest a new TADIR export. Deterministic operations (no LLM sub-agent), idempotent.
lint-audit
Checks the integrity of the abapwiki knowledge base: parseable YAML frontmatter, no broken wikilinks, resolvable [VERIFIED: path:N-M] citations, non-nested confidence tags, drift between wiki and DB, synchronization between canonical agent contracts and the .claude/agents/ copies. Use this skill periodically or after…