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 0k-lab/knowledge-capturenpx agentmods add plugins/0k-lab/knowledge-capture/marketplacegit clone --depth 1 https://github.com/0k-lab/knowledge-captureGrade A, and why
knowledge-capture 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- knowledge-capture — 86% identical, 44 lines differ
What it actually says
{
"name": "knowledge-capture",
"owner": {
"name": "kRicha"
},
"description": "Capture agent decisions, evidence, changes, and next steps as local Markdown.",
"plugins": [
{
"name": "knowledge-capture",
"displayName": "Knowledge Capture",
"source": "./",
"description": "Capture agent decisions, evidence, changes, and next steps as local Markdown.",
"version": "0.7.1",
"author": {
"name": "kRicha",
"url": "https://github.com/kricha"
},
"homepage": "https://github.com/0k-lab/knowledge-capture",
"repository": "https://github.com/0k-lab/knowledge-capture",
"license": "MIT",
"keywords": [
"agent-skill",
"knowledge-capture",
"handoff",
"local-first",
"markdown"
],
"category": "productivity"
}
]
}
What ships with it
1 file beside marketplace.json 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.
- yesterday First seen · 32 lines scan A de9ef0fecd99
knowledge-capture is a plugin published in the GitHub repository 0k-lab/knowledge-capture (2 stars, last pushed 5d 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
pad
Talk to your project. Pad is local-first project management for developers and AI agents — this plugin gives Claude Code a conversational Pad skill, typed shortcuts (/pad:status, /pad:capture, /pad:onboard, /pad:connect, /pad:disconnect), and consent-gated live item-change notifications.
wikimate-marketplace
Plugin marketplace listing 1 plugin: wikimate.
tree-ring-memory
Local-first memory lifecycle, project bootstrap, and receipt-backed harness guidance for Claude Code using Tree Ring Memory v0.15+.
cortex
Remembers your decisions, coding conventions, and debugging lessons across every Claude Code session. Persistent local memory for AI coding agents.
lians
Bitemporal memory for Claude Code with deterministic supersession, point-in-time recall, local MCP, erasure proofs, and tamper-evident history.
memtrace-skills
Memtrace skills for codebase exploration, code search, relationship analysis, temporal evolution, blast radius impact, code quality, graph algorithms, API topology, GitHub PR code review, multi-agent fleet coordination (branch-scoped intents, conflict classification, and agent-judged Class C resolution), and…