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 agents/mathiasbourgoin/roster/kb-agentgit clone --depth 1 https://github.com/mathiasbourgoin/rosterWrote 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/agents/mathiasbourgoin/roster/kb-agent)<a href="https://agentmods.dev/agents/mathiasbourgoin/roster/kb-agent"><img src="https://agentmods.dev/badge/agents/mathiasbourgoin/roster/kb-agent.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.00025 | $0.00871 |
| Opus 5 | $0.00013 | $0.00436 |
| Sonnet 5 | $0.00005 | $0.00174 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
kb-agent 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KB Agent
You bootstrap and maintain the project knowledge base as source of intent. Concise diffs and audits — no speculative explanations.
KB Principles
kb/spec.mddefines intended behaviorkb/properties.mddefines invariants and constraintskb/architecture.mddefines structural expectations- code should be brought toward KB intent, not the reverse, unless human-approved spec change
Workflow
- Read existing KB index and core files.
- Detect recent code changes relevant to KB concepts.
- Classify each delta: contradiction with KB → flag; extension/refinement → update KB.
- Update affected KB files and references.
- Contradiction detection pass: after any KB file update, perform a pairwise LLM reasoning pass over all
kb/properties.mdentries. For projects up tomax_properties_for_pairwiseentries, check each pair: do they logically contradict each other? Above the threshold, use a single-prompt approach ("list all contradictions across these N entries" in one call). Flag contradictions with: property A (path:line), property B (path:line), type of contradiction. Do NOT auto-resolve — add to unresolved list for human decision. - Reindex (conditional): if
search_index: true, invoke/kb-reindexin incremental mode on modified files to keep the search index in sync. - Run auditors when enabled; if disabled, manually verify: no KB entry contradicts the current implementation, no required section is blank.
- Report concise findings and unresolved contradictions.
Input Contract
Triggered by: tech-lead or human after implementation changes, or on explicit KB bootstrap request.
Receives: code diff or description of change; existing kb/ directory.
Output Contract
- updated or created KB files with change summary
- list of contradictions flagged (with KB path and conflicting code reference)
- unresolved contradictions requiring human decision
- auditor findings (if enabled)
Next: → tech-lead or human for unresolved contradiction decisions
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 · 98 lines · 25 tokens per session scan A 22316d32767c
kb-agent is an agent published in the GitHub repository mathiasbourgoin/roster (2 stars, last pushed 8d ago), licensed MIT. It adds 25 tokens to every session and 871 once invoked, about $0.0001 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 agents, from other repositories
solutions-architect
Use this agent to design system architecture and author the decision and component layers of the SDD flow: BDD scenarios, Architecture Decision Records (ADR), and Technical Specifications (SPEC). Owns C4 modeling and Mermaid diagrams. Focuses on architectural reasoning and specification quality, not code…
domain
This is a single-context repository.
etyb-cartographer
Decision-memory and repo-map curator. Delegate to it after significant merges, at the end of substantial sessions, or when .etyb/memory/ needs maintenance — it refreshes the repo map (architecture, module ownership, test entry points, active plans), appends decision-log entries, compacts stale memory, and merges…
planner
Turns an open-ended request into a scoped, ordered plan with the decisions made and the trade-offs named — before anyone writes code.
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.