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.
/plugin marketplace add mrosnerr/open-zk-kbnpx agentmods add plugins/mrosnerr/open-zk-kb/plugingit clone --depth 1 https://github.com/mrosnerr/open-zk-kbGrade A, and why
open-zk-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 yesterday.
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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "open-zk-kb",
"version": "1.4.4",
"description": "Persistent agent memory across sessions. Corrections stick, context compounds, every session starts smarter. Cross-session knowledge base built on Zettelkasten.",
"author": {
"name": "mrosnerr",
"url": "https://github.com/mrosnerr"
},
"homepage": "https://github.com/mrosnerr/open-zk-kb",
"repository": "https://github.com/mrosnerr/open-zk-kb",
"license": "MIT",
"keywords": [
"knowledge-base",
"memory",
"zettelkasten",
"persistent-context",
"mcp",
"cross-session"
]
}
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.
- yesterday First seen · 22 lines scan A dd512d7d2d16
open-zk-kb is a plugin published in the GitHub repository mrosnerr/open-zk-kb (7 stars, last pushed 4d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
kipi
Kipi System plugin marketplace.
kipi-core
Core founder OS — voice, research, AUDHD, LinkedIn/brand, RCA skills + kipi-mcp server.
kipi-dsse
DSSE issue workflow: scope-enforced edits, per-finding dispositions, Codex review gates. Provides /issue-start, /issue-approve, /issue-verify, /issue-review, /issue-amend, /issue-closeout. Consumes issue specs created by prd-os or dropped in manually.
prd-os
PRD operating system: capture rough ideas, draft reviewable PRDs, run standard and adversarial review (Codex or a Claude senior-staff-engineer subagent, recorded truthfully), triage findings, decompose approved PRDs into atomic issue specs, and execute those issues with scope enforcement, stop-gate receipts, and…
kipi-design
Brand, UI/UX, and design skills.
task-orchestrator-marketplace
Server-enforced workflow discipline for AI agents — persistent work items, dependency graphs, note-gated transitions, and actor attribution.