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 assafkip/kipi-systemnpx agentmods add plugins/assafkip/kipi-system/kipi-designgit 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-design)<a href="https://agentmods.dev/plugins/assafkip/kipi-system/kipi-design"><img src="https://agentmods.dev/badge/plugins/assafkip/kipi-system/kipi-design.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
kipi-design 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 5d 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-design",
"version": "1.2.10",
"description": "Brand, UI/UX, and design 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. 3 skills travel with it, and installing the plugin installs all of them — 121 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.
- 5d ago First seen · 13 lines scan A df5361be0483
kipi-design is a plugin published in the GitHub repository assafkip/kipi-system (109 stars, last pushed today), 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.
mock-plugin
Mock plugin for testing integration.
llm-wiki
Official Scraps LLM Wiki bundle. Skills and agents for ingesting sources, querying the wiki, applying the default Scraps LLM Wiki schema, and running purpose-driven lint via the scraps CLI.
mcp-server
MCP server for Scraps - Connect to a locally running scraps MCP server (scraps mcp serve --http) to browse and search interconnected Markdown documentation with Wiki-link notation.
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.