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 skills/techwolf-ai/ai-first-toolkit/kb-answernpx skills add techwolf-ai/ai-first-toolkit --skill kb-answergit clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkitWhat 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.00046 | $0.01373 |
| Opus 5 | $0.00023 | $0.00687 |
| Sonnet 5 | $0.00009 | $0.00275 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade A, and why
kb-answer 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 3d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KB Answer Workflow
Follow these steps in order for every question. For multiple independent questions, use parallel agents.
Prerequisites
Check that kb/ exists in the project root. If not, tell the user to run /setup-knowledge-base first.
Step 1: Navigate Using the Index
Always start by reading the KB index:
kb/index.md
The index provides:
- Keyword Lookup: find the right file by keyword
- Category overview: all files grouped by topic
If the index is empty or outdated, run the index script first:
python3 scripts/kb-index.py
Quick Navigation
- Check the keyword lookup table for matching terms
- Go to the matching file(s)
- If no keyword match, browse the category that best fits the question. Categories can be nested (e.g.,
security/access/) — drill down into sub-groups when a broad category has them.
Step 2: Read Relevant Files
Based on the index navigation:
- Read the most relevant file first
- Check
related:links in the frontmatter if the file references other entries - Read additional files if the first doesn't fully cover the question
Step 3: Search (if needed)
If the index doesn't point to the right file, run the search script to rank entries by keyword across title, tags, description, category, and body:
python3 scripts/kb-search.py "your keyword"
Options worth knowing:
--category securityrestricts to a category (matches nested children likesecurity/accesstoo).--tag mfafilters by frontmatter tag (repeatable).--limit 5caps results.--jsonfor a machine-readable list (useful when chaining into another step).
Fall back to the Grep tool with path kb/ only if the search script misses a term (e.g., regex-only patterns).
Step 4: Check Active Scope
If kb/scopes/ contains scope files beyond _default.yaml:
- Ask the user which scope applies (if not already established in this conversation)
- Read the active scope file
- Apply
in_scope,out_of_scope, andnotesto shape your answer
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.
- 3d ago First seen · 156 lines · 46 tokens per session scan A 9a212887ac23
kb-answer is a skill published in the GitHub repository techwolf-ai/ai-first-toolkit (96 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,373 once invoked, about $0.0002 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-30.
Other skills, from other repositories
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
brainstorming
Use this BEFORE any creative or feature work: building a new feature, adding functionality, changing behavior, or making a nontrivial design decision. Turns the user's request into a validated design — recorded as a spec-graph task-spec — before any implementation. Do not skip this because a change looks small.
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
review
Multi-agent code review for Rust CLI/TUI. UX Review inactive (terminal UI — no web frontend). Code Review only. Includes Rust/clippy-specific checklist.
verify
Self-healing verification loop (test → clippy → fmt).
next
Session start - check progress, suggest next task.