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/statusgit 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/status)<a href="https://agentmods.dev/commands/eduardoabreu81/livewiki/status"><img src="https://agentmods.dev/badge/commands/eduardoabreu81/livewiki/status.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.00707 |
| Opus 5 | $0.00000 | $0.00353 |
| Sonnet 5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
status 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 4d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
livewiki status command
This page documents the CLI command that reports the current health of a livewiki index.
When to use this page
- Run
livewiki statusto see whatrunStatusandformatStatusHumanemit and how--jsonand--topreshape that report. - Inspect
registerStatusto understand how--diffswitches the handler fromrunStatusinto thepreviewWorkingTreeDebtpath. - Review how the command degrades when the working tree is not a git repository.
- Trace the command-level error handling that funnels unexpected throws into a single non-zero exit code.
How it fits
packages/cli/src/commands/status.ts is one of the subcommand registrations wired into the top-level livewiki Commander program. It delegates the actual report and diff work to two sibling modules in @livewiki/core: status (which produces the index report and a human formatter) and diff-preview (which produces the read-only working-tree diff preview and its human formatter). The file itself contains no scanning or git logic — it only adapts CLI flags into the inputs those core helpers expect.
Diagram
%% livewiki/diagrams/commands-status.mmd
Status command registration
The single responsibility of registerStatus is to attach a status subcommand to the Commander program and to translate its flags into the arguments the core helpers understand.
export function registerStatus(program: Command): void
registerStatus takes the shared Command instance and returns nothing; it registers the subcommand as a side effect.
Inside the handler, the file first resolves the repository root (path.resolve(process.cwd(), opts.repo ?? ".")) and parses opts.top into an integer defaulting to 10, then branches on --diff:
- Without
--diff— callsrunStatus(repoRoot, { topN })to produce the index report. The result is either serialized to stdout as{ ok: true, ...report }JSON (when--jsonis set) or rendered throughformatStatusHuman. - With
--diff— callspreviewWorkingTreeDebt(repoRoot)for a read-only pre-commit preview of the anchors the uncommitted working-tree diff would invalidate. The result is again emitted either as JSON or viaformatDiffPreviewHuman.
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.
- 4d ago First seen · 46 lines · 0 tokens per session scan A 97659b9edfe6
status is a command published in the GitHub repository eduardoabreu81/livewiki (0 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 707 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…
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…
query
Queries the abapwiki knowledge base to answer questions about custom ABAP code (what an object does, which tables it uses, who calls it, dependencies, bugs). Navigates index -> package -> pages; can extend the answer with the SAP system via MCP abap-fs in read-only mode, explicitly citing wiki vs. system.
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…