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/dinosn/security-knowledge-base/security-kbnpx skills add dinosn/security-knowledge-base --skill security-kbgit clone --depth 1 https://github.com/dinosn/security-knowledge-baseWhat 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.00092 | $0.01436 |
| Opus 5 | $0.00046 | $0.00718 |
| Sonnet 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 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.
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.
- 3d 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 (9 stars, last pushed 21d ago), licensed MIT. It adds 92 tokens to every session and 1,436 once invoked, about $0.0005 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 skills, from other repositories
implementing-api-schema-validation-security
Implement API schema validation using OpenAPI specifications and JSON Schema to enforce input/output contracts and prevent injection, data exposure, and mass assignment attacks.
web-app-penetration-testing
Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature…
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
imsg
Use imsg to read and send iMessage/SMS via macOS Messages.app.
finding-protocol
Operational-tier finding template — minimal fields for sub-agent decision support. Heavyweight deliverable promotion lives in skills/decepticon/final-report.