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/install)<a href="https://agentmods.dev/commands/eduardoabreu81/livewiki/install"><img src="https://agentmods.dev/badge/commands/eduardoabreu81/livewiki/install/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/install"><img src="https://agentmods.dev/badge/commands/eduardoabreu81/livewiki/install.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.01782 |
| Opus 5.5 | $0.00000 | $0.00713 |
| Sonnet 5.5 | $0.00000 | $0.00356 |
| Haiku 4.5 | $0.00000 | $0.00178 |
Grade A, and why
install 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LiveWiki Install Command Orchestration
This page explains how the livewiki install CLI command detects installed coding agents and safely configures the livewiki MCP server entry, hook templates, shared skills, and optional pointer files.
When to use this page
- Understand the full user flow of the
installcommand, from option parsing to applying changes. - Trace how the command validates user input and enforces safety checks before any file is written.
- Learn how the command formats its output for both human-readable terminal display and JSON consumption.
How it fits
This module is the command-layer implementation for the livewiki CLI, responsible for coordinating the core @livewiki/core/install package. It handles user-facing concerns like option parsing, interactive prompting, and output formatting, then delegates the actual detection, planning, and application of changes to the core package's functions. The file is part of the CLI's command set, alongside other commands registered on the same commander program, and relies on shared helpers for emitting output and resolving the repository root.
The command's central policy is safety: it shows the user every intended action before writing anything, supports a full dry-run via --print, and refuses to write in non-interactive mode unless explicitly told to with --yes. It also implements an opt-in rule for writing pointer files, requiring a dedicated flag or an additional interactive confirmation.
Diagram
%% livewiki/diagrams/commands-install.mmd
Option Validation and Command Registration
This section is the entry point for the entire command. registerInstall exists to wire the install subcommand into the CLI's commander program, defining its options and the action that runs when the user invokes it. The function takes the program object and returns nothing; it registers the command, its description, all its flags, and the async callback that implements the command's behavior.
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 · 126 lines · 0 tokens per session scan A 5f1c6f9f1a94
install is a command published in the GitHub repository eduardoabreu81/livewiki (1 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,782 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
landing-publish
Use this command to publish landing pages to the seite site as pages.
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-refresh
Re-fetch a cached source, ignoring the 7-day cache. Use when upstream content has changed.
web-refresh
Re-fetch a cached web source, ignoring the 7-day cache. Use when upstream content has changed.
docs-list
List source aliases currently cached locally, with last-fetched age.
publish-draft
Publish a draft article from content/ by removing the draft: true flag, building the site, and optionally deploying.