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 skills add dinosn/security-knowledge-base --skill security-kbgit clone --depth 1 https://github.com/dinosn/security-knowledge-baseWrote 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/skills/dinosn/security-knowledge-base/security-kb)<a href="https://agentmods.dev/skills/dinosn/security-knowledge-base/security-kb"><img src="https://agentmods.dev/badge/skills/dinosn/security-knowledge-base/security-kb/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/skills/dinosn/security-knowledge-base/security-kb"><img src="https://agentmods.dev/badge/skills/dinosn/security-knowledge-base/security-kb.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.00092 | $0.01436 |
| Opus 5.5 | $0.00037 | $0.00574 |
| Sonnet 5.5 | $0.00018 | $0.00287 |
| Haiku 4.5 | $0.00009 | $0.00144 |
Grade A, and why
security-kb 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 2mo 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.
Use the Security Knowledge Base
Treat this skill as a portable workflow adapter. The selected repository's
AGENTS.md, docs/protocol/v1.md, schemas, live capabilities, and kb runtime
remain authoritative. Do not copy knowledge records into this skill.
Select the repository
-
Locate the intended repository root by finding
kb.json,AGENTS.md, and thekbentrypoint. If more than one candidate exists, do not combine them; select the boundary named by the user or ask which boundary to use. -
Work from that repository root. Read
AGENTS.mdanddocs/protocol/v1.mdcompletely. -
Run:
./kb --json capabilities ./kb --json status -
Require protocol major
1,agent_writes: ["proposals"], and falsenetwork,source_execution, andarchive_extractioncapabilities. -
Require the intended
boundary_idand classification andintegrity: ok. Notedirtystate, but do not let unrelated worktree changes prevent read-only inspection. Before preparing or staging a new proposal, require a clean baseline and a non-null Git revision. After staging, the new proposal makes the worktree dirty by design; still validate that exact bundle and run lint.tenant_idin records and requests must equalboundary_id. -
Remember that
boundary_idis not access control. Repository permissions, identities, storage, and separate checkouts enforce isolation. -
Stop and report any conflict between policy, schemas, protocol, and runtime.
For every command, check the process exit status and the JSON envelope. Require
schema: skb.command-result/v1, supported versions, ok: true, and an
appropriate trust value before using result. Inspect warnings. Preserve a
failure's error.code, error.message, and error.details exactly.
Read and search
Use bounded operations such as:
./kb --json list --type claims --limit 100
./kb --json list --type findings --limit 100
./kb --json search "QUERY" --type all --limit 50
./kb --json get OBJECT_ID
./kb --json source excerpt SOURCE_ID --start-byte 0 --length 4096
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 156 lines · 92 tokens per session scan A 3a32ba398ea4
security-kb is a skill published in the GitHub repository dinosn/security-knowledge-base (10 stars, last pushed 2mo ago), licensed MIT. It adds 92 tokens to every session and 1,436 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
create-tech-design
Only use when the user explicitly invokes this skill by name.
iterate-tech-design
Only use when the user explicitly invokes this skill by name.
implement-outline
Only use when the user explicitly invokes this skill by name.
iterate-implementation
Only use when the user explicitly invokes this skill by name.
create-plan
Only use when the user explicitly invokes this skill by name.
show-me
Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.