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 skills add eduardoabreu81/livewiki --skill document-as-you-gogit 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/skills/eduardoabreu81/livewiki/document-as-you-go)<a href="https://agentmods.dev/skills/eduardoabreu81/livewiki/document-as-you-go"><img src="https://agentmods.dev/badge/skills/eduardoabreu81/livewiki/document-as-you-go/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/skills/eduardoabreu81/livewiki/document-as-you-go"><img src="https://agentmods.dev/badge/skills/eduardoabreu81/livewiki/document-as-you-go.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.00050 | $0.01414 |
| Opus 5 | $0.00025 | $0.00707 |
| Sonnet 5 | $0.00010 | $0.00283 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
document-as-you-go 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 10d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
document-as-you-go
Você acabou de fechar uma tarefa, um commit, ou um lote de mudanças. Antes de parar, pague a dívida de documentação da wiki. Quem fez a mudança documenta melhor — você tem o contexto fresco na cabeça, e isso custa zero tokens de API.
Quando usar
Após cada uma destas ações, ANTES de parar a sessão:
- Fechou um commit
- Terminou uma task / subtask
- Fez merge de um branch
- Deixou o trabalho num estado "completo por agora"
Não use no meio de uma edição ativa — espere o trabalho estar fechado.
O que fazer
1. Veja a dívida
livewiki status --json
Procure debt.items no JSON. Se vazio, pare aqui — não tem dívida a pagar.
2. Emita o pacote de trabalho
livewiki update --json
Lê o JSON. Ele contém:
debt: lista de itens (changed/moved/deleted) comsymbol_key,wiki_path,assignee. Você só precisa pagar os deassignee=agent(oshumansão páginas de negócio que precisam de revisão humana — não toque).snippets: janelas do source atual em torno de cada âncora. Use como contexto — você não precisa reler o arquivo.validAnchors: as chaves canônicas que você pode ancorar (symbols ativos). Distribua essas chaves pelas seções da página — nunca invente chave fora dessa lista.tokensEstimated: tamanho do pacote (heurística chars/4). Tese do produto: esse número é MENOR que reler o repo inteiro. Mantenha assim.
3. Pague cada item — 2 caminhos
Caminho A (preferido): MCP livewiki_write_doc
Você (agente) tem o tool MCP do livewiki. Para cada dívida:
- Leia a wiki page correspondente com
livewiki_read - Atualize o conteúdo: adicione a âncora na seção certa, corrija a descrição conforme o snippet novo
- Chame
livewiki_write_doccom o path completo da wiki page e o conteúdo atualizado. Ele rodaverifyantes de aceitar — se anchor quebrar, é rejeitado. Corrija e re-tente.
Caminho B (manual): edição direta + verify
Se você não tem o MCP (ex.: agente sem MCP configurado), edite o arquivo
livewiki/<wiki_path>.md direto no disco, depois:
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.
- 10d ago First seen · 149 lines · 50 tokens per session scan A 44855c27651b
document-as-you-go is a skill published in the GitHub repository eduardoabreu81/livewiki (1 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 1,414 once invoked, about $0.0003 per session on Opus 5. 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 skills, from other repositories
eval
Measure retrieval quality — Hit@5, MRR, Precision@5 on a fixed fixture set, or Hit@5/MRR/nDCG@10 on your own corpus via the real-corpus benchmark. Regression tracking against a saved baseline, plain-English interpretation, and tuning pointers when numbers look off. Use after every ingest or config change.
ingest
Populate the gnosis-mcp knowledge base — from local files, git history, or a crawled website. Handles the full matrix of flags (--force, --prune, --wipe, --embed, --include-crawled) in one place.
manage
CRUD operations on the knowledge base — add, delete, update metadata. For bulk ingest / re-ingest / prune, use /gnosis:ingest instead. Requires GNOSISMCPWRITABLE=true.
search
Search the gnosis-mcp knowledge base. Keyword (default), hybrid semantic+keyword (--semantic), or git commit history (--git). Includes sanity checks and a reranker warning.
setup
First-time setup wizard for Gnosis MCP. Install, init the database, ingest a docs folder, wire your editor — in that order.
status
Verify gnosis-mcp server connectivity, schema integrity, and corpus health. Use when MCP calls fail, return empty, or return unexpected data.