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/assafkip/kipi-systemWrote 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/assafkip/kipi-system/kipi-ops)<a href="https://agentmods.dev/plugins/assafkip/kipi-system/kipi-ops"><img src="https://agentmods.dev/badge/plugins/assafkip/kipi-system/kipi-ops/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/assafkip/kipi-system/kipi-ops"><img src="https://agentmods.dev/badge/plugins/assafkip/kipi-system/kipi-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
kipi-ops 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": "kipi-ops",
"version": "1.2.0",
"description": "GTM and council skills",
"author": { "name": "Assaf Kipnis", "email": "[REDACTED]" },
"repository": "https://github.com/assafkip/kipi-system",
"license": "MIT",
"skills": "./skills/"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 22 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 · 10 lines scan A a1130be2a2ec
kipi-ops is a plugin published in the GitHub repository assafkip/kipi-system (121 stars, last pushed 2d 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-30.
Other plugins, from other repositories
mnemonic
Pure filesystem-based memory system for Claude Code with custom ontology support.
hipocampus
Persistent agent memory that survives across sessions — auto-compacting 3-tier memory with hybrid search. Your agent remembers what it learned, decided, and built.
context-canopy
Portable personal AI context: search and capture knowledge, then read allowlisted user authority across agents.
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.
remember
Extended Second Brain that learns as you work in Claude Code.
ConsiderateCoder
Development methodology plugin: Clean Architecture x TDD x three-tier delegation (communicator / orchestrator / worker) with /plan-sdd, /outsource, /dig and /refactor commands.