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-output)<a href="https://agentmods.dev/commands/thomascasali/claude-kb-workflow/kb-output"><img src="https://agentmods.dev/badge/commands/thomascasali/claude-kb-workflow/kb-output.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.1 | $0.00000 | $0.00785 |
| Opus 5 | $0.00000 | $0.00392 |
| Sonnet 5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
kb-output 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 7d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/kb-output — Esporta wiki page come presentazione Marp
Esporta una pagina della LLM Wiki in formato slide deck Marp: $ARGUMENTS
Path:
$LLM_WIKI_PATHper la wiki sorgente.
Parsing argomenti
- Formato:
/kb-output [pagina] [--slides|--summary|--report] - Esempi:
/kb-output flutter-architecture --slides/kb-output nome-progetto --summary/kb-output --slides(senza pagina = genera slides per tutti i concepts)
Steps
Modalità --slides (default)
-
Leggi la pagina wiki specificata da
$LLM_WIKI_PATH/wiki/- Se è un progetto:
wiki/projects/[pagina].md - Se è un concetto:
wiki/concepts/[pagina].md
- Se è un progetto:
-
Genera un file Marp nella cartella
$LLM_WIKI_PATH/output/:- Nome file:
YYYY-MM-DD-[pagina].md - Frontmatter obbligatorio:
--- marp: true theme: default paginate: true backgroundColor: #1a1a2e color: #eee style: | section { font-family: 'Segoe UI', sans-serif; } h1 { color: #e94560; } h2 { color: #0f3460; } code { background: #16213e; } --- - Struttura slide per progetto:
- Slide 1: Titolo + Stack + Data
- Slide 2: Quick Reference (repo, server, comandi deploy)
- Slide 3-N: Stato corrente, sezioni principali
- Slide finale: Open Questions + Link KB
- Struttura slide per concetto:
- Slide 1: Titolo + definizione
- Slide 2-N: Pattern principali con code blocks
- Slide finale: Progetti che usano questo concetto
[[wikilinks]]
- Nome file:
-
Mostra il comando di esportazione da eseguire:
# Preview nel browser npx @marp-team/marp-cli $LLM_WIKI_PATH/output/[file].md -o output.html --allow-local-files # PDF npx @marp-team/marp-cli $LLM_WIKI_PATH/output/[file].md --pdf -o output.pdf # PPTX npx @marp-team/marp-cli $LLM_WIKI_PATH/output/[file].md --pptx -o output.pptx
Modalità --summary
Genera un riassunto testuale della pagina in 5-10 bullet points. Utile per quick review prima di una sessione su quel progetto.
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.
- 7d ago First seen · 81 lines · 0 tokens per session scan A 3995a2b89c6a
kb-output is a command published in the GitHub repository thomascasali/claude-kb-workflow (2 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 785 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
onboarding
Guided first run — from a fresh project to a working, queryable wiki in five short steps. Safe to re-run; resumes from wherever you are.
brand-generate
Generate an on-brand document from a saved Brand Profile.
tidy
Consistency check for non-code repos with INDEX.md hierarchy. Verifies INDEX.md accuracy, MEMORY.md references, orphaned files, stale dates, and WAITING markers.
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…
batch-execute
Execute a batch of ops plans continuously without user input, storing any issues and user questions in a .md file to be processed with the user afterwards. Do NOT invoke this yourself! Should only be invoked by the user.
standup
Dev standup — open Linear tickets grouped by in-flight, top priority, and backlog.