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.
npx skills add memi-design/memi --skill remember-design-systemgit 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/skills/memi-design/memi/remember-design-system)<a href="https://agentmods.dev/skills/memi-design/memi/remember-design-system"><img src="https://agentmods.dev/badge/skills/memi-design/memi/remember-design-system/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/skills/memi-design/memi/remember-design-system"><img src="https://agentmods.dev/badge/skills/memi-design/memi/remember-design-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00039 | $0.00505 |
| Opus 5.5 | $0.00016 | $0.00202 |
| Sonnet 5.5 | $0.00008 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
remember-design-system 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.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remember The Design System
Build design context from the repository instead of guessing from the prompt. This is a preflight for UI work, not a request to redesign the product.
This workflow targets published beta 2.8.0-beta.2. Use npx -y @memi-design/[email protected] --version to verify the exact package; a local memi must report that same version before these recipes run. The independent stable compatibility baseline is 2.7.9. See current release state and known limitations. npm availability alone does not establish native-binary success.
Build The Brief
Translate the user's task into a short intent, then run from the repository root:
memi agent brief . --frontend --intent "<user's interface task>" --max-bytes 16384 --json
The frontend brief already includes bounded token and story evidence. For a selected Figma or Paper node, use the harness connector and supply its normalized evidence:
memi agent brief . --frontend --intent "<task>" --design-evidence design/selected-node.json --json
Apply The Memory
- Prefer existing components and the project's conventions. Do not impose a new component library or CSS framework.
- Map every new component to atom, molecule, organism, template, or page.
- Reuse semantic CSS variables and Tailwind theme tokens. Do not introduce raw hex values when a token exists.
- Preserve route, state, loading, empty, error, focus, and responsive behavior identified by the brief.
- Resolve stale/conflicting mappings and missing required props before editing. Read cited source files when the bounded brief omits needed details.
- Treat inferred story IDs and host-supplied mappings as evidence, not rendered verification. Run the actual project tests.
Handoff
Before editing, state the components and tokens you will reuse. After editing, cite files changed, evidence followed, checks run, and any design assumptions that remain.
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 · +3 lines 0e2373e1d954
- 1mo ago First seen · 35 lines · 39 tokens per session scan A d49206354f11
remember-design-system is a skill published in the GitHub repository memi-design/memi (47 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 505 once invoked, about $0.0002 per session on Opus 5.5. 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 skills, from other repositories
homespun
Deploy a real multi-user web app from this conversation, then keep operating it. You author an HTML page plus a manifest; homespun deploy puts it live on its own URL with magic-link sign-in, a shared realtime database, per-role read/write/delete permissions, email notifications and file uploads. Owners invite other…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
scaffold-project
Scaffold a new app, API, backend, fullstack project, mobile app, polyglot service, monorepo, or starter with Better Fullstack. Use when the user wants to create, start, bootstrap, initialize, or generate a project from a stack description. Prefer the bundled Better Fullstack MCP server: guidance, schema…
add-to-project
Add capabilities, addons, deployment targets, generated CI, services, or stack updates to an existing Better Fullstack project. Use when the current repo has bts.jsonc or the user asks to extend a generated project. Prefer bfsplanstackupdate and bfsapplystackupdate; use legacy addon tools only for addon/deploy-only…
frontmcp-extensibility
Use when extending FrontMCP beyond the core SDK by integrating external npm packages, libraries, or third-party services into providers and tools. Covers VectoriaDB for in-memory semantic and vector search (ML-based embeddings or TF-IDF keyword engines, with persistence) and the tamper-evident, hash-chained skill…
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…