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/memi-design/memiWrote 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/memi-design/memi/memi-claude)<a href="https://agentmods.dev/plugins/memi-design/memi/memi-claude"><img src="https://agentmods.dev/badge/plugins/memi-design/memi/memi-claude/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/memi-design/memi/memi-claude"><img src="https://agentmods.dev/badge/plugins/memi-design/memi/memi-claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memi 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": "memi",
"description": "Memi is the design layer for agentic AI.",
"version": "2.8.0-beta.2",
"author": {
"name": "Sarvesh Chidambaram",
"url": "https://github.com/sarveshsea"
},
"homepage": "https://www.memoire.cv/docs",
"repository": "https://github.com/sarveshsea/memi",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 167 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 Changed 3b8a4455d122
- 1mo ago First seen · 13 lines scan A 36e7fabd79e3
memi is a plugin published in the GitHub repository memi-design/memi (47 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
better-fullstack
Let your AI assistant scaffold and extend Better Fullstack projects through the official MCP server and focused skills.
pipefy
Pipefy MCP for Claude Code. Sign in through the browser to manage pipes, cards, tables, reports, automations, and AI agents, and use the included skills to build and analyze processes.
faf
Persistent Project Context for AI — IANA-registered .faf format. Run /faf to score your project in Claude Code; install the CLI via bunx faf or npm install -g faf-cli for the full toolkit.
qamap
Review a pull request from one local brief: the diff, the tests and callers of changed code, and change signals. No LLM call, no upload.
skills-for-figma
18 skills for the native Figma MCP: export/import design tokens, manage variables, analyze and document component sets, lint for WCAG and design-system compliance, audit accessibility, and author Slides and FigJam content.
figma-design-skills
Two composable skills for design-to-code fidelity: figma-design-extract pulls exact specs from Figma into a build-ready spec table; design-fidelity-verify proves the running web or mobile app matches them by measuring rendered values.