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.
git clone --depth 1 https://github.com/zimalabs/code-decisionsWrote 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/plugins/zimalabs/code-decisions/src)<a href="https://agentmods.dev/plugins/zimalabs/code-decisions/src"><img src="https://agentmods.dev/badge/plugins/zimalabs/code-decisions/src/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/plugins/zimalabs/code-decisions/src"><img src="https://agentmods.dev/badge/plugins/zimalabs/code-decisions/src.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
decisions 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 1mo 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.
What it actually says
{
"name": "decisions",
"version": "1.4.0",
"description": "Gives your codebase a memory for why. Captures decisions automatically, surfaces them when you edit affected files.",
"author": {
"name": "Zima Labs",
"url": "https://github.com/zimalabs"
},
"repository": "https://github.com/zimalabs/code-decisions",
"homepage": "https://github.com/zimalabs/code-decisions",
"license": "MIT",
"keywords": [
"decisions", "memory", "context", "architecture-decisions", "ADR",
"decision-log", "rationale", "reasoning", "knowledge-management",
"project-history", "onboarding"
]
}
What it installs
The manifest is a name and a version. 1 skill, 5 hooks travel with it, and installing the plugin installs all of them — 23 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 18 lines scan A 07145656d36d
decisions is a plugin published in the GitHub repository zimalabs/code-decisions (5 stars, last pushed 3mo 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
tsubasa
Captain persona: repo-resident domain expert with a git-stored knowledge graph, ambient knowledge capture, and ADR-threaded delegation.
toonify-mcp
Local context compression for Claude Code workflows, including structured data and debug-heavy output.
claude-mega-brain
OKF-powered knowledge context for Claude Code — injects your project knowledge base at every session.
captain-memo
Cross-AI local memory layer for Claude Code, Codex, Gemini CLI, Antigravity, goose, Cursor, opencode, Kimi CLI and more: hybrid search, six summarizer providers, hosted or local embedder. Replaces claude-mem.
continuity
Durable project state across AI sessions: decisions, constraints, and rejected paths, versioned in git as plain markdown. Not a memory tool — it answers what is true about the project now, and what must not change.
handoff
Portable project memory + development workflow for coding agents: auto-loads STATUS+RULES each session, enforces folder-level CONTEXT.md on edit, nudges durable state updates at turn end, scaffolds the system into any repo via guided discovery, and ships a tiered 6-phase workflow skill set covering every phase (brief.