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/oliver-zehentleitner/keep-the-whyWrote 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/oliver-zehentleitner/keep-the-why/keep-the-why)<a href="https://agentmods.dev/plugins/oliver-zehentleitner/keep-the-why/keep-the-why"><img src="https://agentmods.dev/badge/plugins/oliver-zehentleitner/keep-the-why/keep-the-why.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
keep-the-why 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
{
"name": "keep-the-why",
"version": "0.12.0",
"description": "Preserves or recovers the reasoning behind a codebase - decisions, rejected alternatives, workarounds, and incident learnings the code alone can't explain.",
"author": {
"name": "Oliver Zehentleitner",
"url": "https://github.com/oliver-zehentleitner"
},
"homepage": "https://keepthewhy.com",
"repository": "https://github.com/oliver-zehentleitner/keep-the-why.git",
"license": "MIT",
"keywords": [
"documentation",
"context",
"decision-log",
"knowledge-management",
"onboarding",
"agents"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 50 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.
- yesterday Changed 6468ca69e366
- 4d ago Changed 93c44f35271b
- 9d ago First seen · 21 lines scan A b827d2856048
keep-the-why is a plugin published in the GitHub repository oliver-zehentleitner/keep-the-why (152 stars, last pushed yesterday), 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-30.
Other plugins, from other repositories
rp1-base
Core knowledge management, documentation generation, and strategic analysis for Claude Code.
memory-kit
Persistent memory for your agent as plain files in your folder: a hot cache injected every session and held under three size caps, per-session handoffs, and promotion into knowledge articles and rules only on your yes. Carries the builder's layers too — executor/recon/idea-validator agents, session review, second…
gnosis
Zero-config knowledge base MCP server — search, manage, and embed documentation (SQLite default, PostgreSQL optional).
aictx
Use AICTX repo-local operational continuity in Claude Code.
trove
Repository memory for Claude Code: index symbols and architecture, progressively retrieve context beyond the context window, and capture durable engineering decisions in a personal trove.
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.