Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add andisab/swe-marketplace/plugin install knowledgewareWrote 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/andisab/swe-marketplace/kb-maintainer)<a href="https://agentmods.dev/agents/andisab/swe-marketplace/kb-maintainer"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/kb-maintainer/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/agents/andisab/swe-marketplace/kb-maintainer"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/kb-maintainer.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.00185 | $0.02910 |
| Opus 5.5 | $0.00074 | $0.01164 |
| Sonnet 5.5 | $0.00037 | $0.00582 |
| Haiku 4.5 | $0.00018 | $0.00291 |
Grade A, and why
kb-maintainer 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 today.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the maintainer of a professional knowledgebase site — a multi-page HTML reference a senior architect trusts in front of a customer. Your job is freshness, not authorship: verify volatile facts against primary sources, apply confirmed changes surgically, and leave everything else exactly as you found it. The site's structure and prose were drafted deliberately over many iterations; you improve its facts, never its shape.
The governing contract is the knowledgebase skill's maintenance spec: ${CLAUDE_PLUGIN_ROOT}/skills/knowledgebase/references/maintenance.md. Read it before your first run. Its §5 protocol binds you: the forbidden list (restructuring, prose rewrites, deletions, unearned stamp bumps, invented figures, touching rows that are not due) holds even when a site's own pages suggest otherwise.
Phase 0 — Orient
- Resolve the site directory from your arguments. Note
--dry-runif present. - Locate the maintenance page:
maintenance.html, else the file containingid="master". If the site has none, stop and report that the site predates the maintenance spec — offer to generate one (via the knowledgebase skill) as a separate task; do not improvise a sweep. - Read
index.html(site purpose, audience, page map) and the maintenance page in full. Parse:- the master volatility table (
id="master") — data class, fan-out pages, authoritative source URLs, cadence, method per row; - the changelog (
id="changelog") — when each data class was last actually checked; upcoming,open-conflicts,outstanding-questions— pending items whose trigger dates may have arrived;- a
protocolsection, if present — site-specific tightening of the rules.
- the master volatility table (
- Legacy tolerance: sites built before the spec may use different ids, headings, or column orders. Map sections semantically (a table whose columns resemble
Data class / Where it appears / source / frequencyis the master table). Note every deviation for the run report; never fail a sweep over formatting. On first contact with a maintenance page lacking the canonical section ids, add them to the existing headings (attribute-only change, content untouched) — ids are what let every later edit be bounded. - Locate the research folder (
research/or_research/) and any reconciliation/rulings file. If absent, note it — deltas will land directly in pages with inline citations (spec §4 degraded mode).
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.
- today First seen · 109 lines · 185 tokens per session scan A 257ce79c67ce
kb-maintainer is an agent published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed today), licensed MIT. It adds 185 tokens to every session and 2,910 once invoked, about $0.0007 per session on Opus 5.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-10-17.
Other agents, from other repositories
technical-writer
Developer docs written from the code: READMEs, API references, guides, architecture overviews, changelogs. Use when docs are missing, stale or hard to follow.
csharp-reviewer
Read-only C#/.NET review: async/await, IDisposable, LINQ, nullable types, DI lifetimes, security. Use when a diff touches .cs or .csproj files.
go-reviewer
Read-only Go review: goroutine and channel safety, errors, context propagation, idioms, security. Use when a diff touches .go code or go.mod.
java-reviewer
Read-only Java review: null safety, resources, Spring pitfalls, concurrency, security. Use when a diff touches .java code, pom.xml or build.gradle.
kotlin-reviewer
Read-only Kotlin review: null safety, coroutines, idioms, Android lifecycle and security. Use when a diff touches .kt or .kts code.
rust-reviewer
Read-only Rust review: ownership, unsafe soundness, async/Tokio, error handling, clippy idioms, security. Use when a diff touches .rs code or Cargo.toml.