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/thomascasali/claude-kb-workflowWrote 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/thomascasali/claude-kb-workflow/kb-promote)<a href="https://agentmods.dev/commands/thomascasali/claude-kb-workflow/kb-promote"><img src="https://agentmods.dev/badge/commands/thomascasali/claude-kb-workflow/kb-promote/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/thomascasali/claude-kb-workflow/kb-promote"><img src="https://agentmods.dev/badge/commands/thomascasali/claude-kb-workflow/kb-promote.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.00584 |
| Opus 5 | $0.00000 | $0.00292 |
| Sonnet 5 | $0.00000 | $0.00117 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
kb-promote 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 9d 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.
What it actually says
/kb-promote — Promuovi un concetto dalla Wiki alla KB stabile
Promuovi il concetto specificato da llm-wiki/wiki/concepts/ alla KB stabile (questo repo o un fork): $ARGUMENTS
Path:
$LLM_WIKI_PATHper la wiki,$KB_PATHper la KB stabile (es. clone locale diclaude-kb-workflow).
Criteri di eleggibilità (verifica prima di procedere)
- Appare in ≥ 2 progetti diversi
- Stabile da ≥ 2 sessioni (controlla
wiki/log.md) - Verificato in produzione (non solo teorico)
- Non già presente in
$KB_PATH/patterns/patterns.mdo$KB_PATH/patterns/field-notes-it.md
Steps
- Leggi
$LLM_WIKI_PATH/wiki/concepts/[concetto].md - Verifica i criteri sopra — se non soddisfatti, avvisa l'utente e fermati
- Identifica destinazione in
$KB_PATH/:- Pattern riusabile cross-progetto →
patterns/patterns.md(aggiungi sezione) - Convenzione personale (deploy, naming, provider) →
patterns/field-notes-it.md - Pattern specifico per stack → aggiorna agente rilevante
agents/[agente].md - Guida operativa →
knowledge-base/[NOME].md
- Pattern riusabile cross-progetto →
- Aggiungi il pattern con formato coerente agli altri (vedi convenzioni in
CONTRIBUTING.md) - Aggiorna
wiki/concepts/[concetto].mdcon nota:> **Promosso** a `KB/[destinazione]` il YYYY-MM-DD - Appendi a
wiki/log.md:| YYYY-MM-DD | PROMOTE | [concetto] | Promosso a KB/[destinazione] | - Commit su entrambi i repo:
git -C $LLM_WIKI_PATH commit -m "wiki: promote [concetto]" git -C $KB_PATH commit -m "kb: add pattern [concetto] (from llm-wiki)"
Filosofia
La promozione è un rito di stabilizzazione: una conoscenza nasce sporca nelle sessioni, viene sintetizzata nella wiki, e solo dopo prove ripetute "guadagna" il posto nella KB stabile.
Questo evita il rumore: la KB resta piccola, focalizzata, autorevole. La wiki resta viva, sperimentale, mutevole.
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.
- 9d ago First seen · 43 lines · 0 tokens per session scan A 96a24325a06b
kb-promote is a command published in the GitHub repository thomascasali/claude-kb-workflow (2 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 584 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
wiki
Run the LLM Wiki — initialize, ingest, curate, or query. The plugin probes vault state and chooses the right next step.
wiki-digest
Generate a daily or weekly digest of wiki changes — new sources, pages, insights, and gaps.
wiki-status
Show wiki health overview — source count, page stats, orphan count, last activity dates.
ccr
CCR (Compressed Context with Retrieval) — recall the full original of context that greatcto compressed/filtered out, by its short id. The retrieval half of the compression layer.
ask
Query the MindBase wiki — cited answer using hybrid search + graph expansion. Usage: /mb:ask [-p ] [--all-projects].
recap
Summarize what happened in the project since a given date. Produces a short lead on what's different now, backed by tables and lists covering completed work, state changes, backlog movement, and key decisions. Use when the user wants to catch up on project activity, review recent progress, or generate a status update…