Borrowing it
Nothing to install: this file belongs to miapre/mimic-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/miapre/mimic-ai/main/CLAUDE.mdgit clone --depth 1 https://github.com/miapre/mimic-aiWrote 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/instructions/miapre/mimic-ai/claude-md)<a href="https://agentmods.dev/instructions/miapre/mimic-ai/claude-md"><img src="https://agentmods.dev/badge/instructions/miapre/mimic-ai/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.06938 | $0.06938 |
| Opus 5 | $0.03469 | $0.03469 |
| Sonnet 5 | $0.01388 | $0.01388 |
| Haiku 4.5 | $0.00694 | $0.00694 |
Grade A, and why
mimic-ai CLAUDE.md 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 7d 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 — 664 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mimic AI
MCP server that builds production-ready Figma using the design system on the user's target file. Accepts prompts, HTML, or any description. Uses real components, tokens, and auto-layout. Learns from every build.
Prerequisites
- FIGMA_TOKEN must be set in the MCP server config
(or in
~/.mimic-ai.jsonas fallback). Without it, Mimic cannot read the library's components or text styles. Generate one in Figma: avatar (top-left) → Settings → Security → Personal access tokens → "Generate new token" (name: "Mimic AI", 90-day expiration). Five scopes required (all read-only):current_user:read,file_content:read,file_metadata:read,library_assets:read,library_content:read. Mimic validates the token on every build and guides users through setup or renewal if missing/expired. - Library file key is prompted once per library and
cached permanently. The user copies it from the library
file's URL:
figma.com/design/<this-part>/... - Figma plugin must be running. In Figma desktop: Plugins > Development > Mimic AI > Run. The bridge connects automatically on first tool call.
- fileKey is the alphanumeric string in the Figma URL:
figma.com/design/<fileKey>/...— pass it tomimic_discover_ds. - Start every build with
mimic_status. It returns the current phase and tells you what to do next. - Don't guess variable paths. Discovery populates the
cache. Use
figma_list_ds(kind:"variables"or"text_styles") to see what's available.
Component-First Principle
Target ~90% DS component usage, ~10% primitives with DS
variables. Every build should maximize DS component coverage.
Before creating ANY frame, check if the DS has a component for
it. Section-level elements (header, footer, sidebar) and UI
patterns (cards, metrics, tables, badges, buttons, inputs)
should ALWAYS be DS components. Only use figma_create_frame
for truly custom layouts that have no DS equivalent — and even
then, bind every property to DS variables and text styles.
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.
- 7d ago First seen · 664 lines · 6,938 tokens per session scan A 1aada08f6657
mimic-ai CLAUDE.md is an instructions file published in the GitHub repository miapre/mimic-ai (13 stars, last pushed 1mo ago), licensed MIT. It adds 6,938 tokens to every session, about $0.0347 per session on Opus 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.