Borrowing it
Nothing to install: this file belongs to kenneives/design-token-bridge-mcp. 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/kenneives/design-token-bridge-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/kenneives/design-token-bridge-mcpWrote 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/kenneives/design-token-bridge-mcp/claude-md)<a href="https://agentmods.dev/instructions/kenneives/design-token-bridge-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/kenneives/design-token-bridge-mcp/claude-md/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/instructions/kenneives/design-token-bridge-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/kenneives/design-token-bridge-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00556 | $0.00556 |
| Opus 5 | $0.00278 | $0.00278 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
design-token-bridge-mcp 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 10d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
design-token-bridge-mcp
Project Overview
MCP server that translates design tokens between Tailwind, Figma, CSS, Material 3, SwiftUI, and CSS Variables.
Publishing Checklist
When making code changes that affect the build output, you must republish:
- Bump version in both
package.jsonandserver.json(keep in sync) - Update version in
src/index.tsMcpServer constructor to match - Build:
npm run build - Test:
npm test(all 91+ tests must pass) - Publish to npm:
npm publish(uses granular access token configured vianpm config set) - Publish to MCP registry:
npx @anthropic-ai/mcp-publisher@latest publish(requiresmcp-publisher login githubfirst) - Push to GitHub:
git push origin main
Key Architecture
- Universal token schema (
src/schemas/universal-token-schema.ts) is the canonical interchange format - 4 extractors (Tailwind, CSS, Figma, DTCG) parse inputs into universal tokens
- 5 generators/validators (Material 3, SwiftUI, Tailwind, CSS vars, contrast) output from universal tokens
- All tool I/O uses Zod schemas for validation
- No eval/Function — Tailwind config extraction uses regex-only static analysis
Testing
npm test— vitest unit testsnpm run test:e2e— Playwright visual tests (QT Games landing page)
TODO
- awesome-mcp-servers badge: PR #2162 at punkpeye/awesome-mcp-servers is still OPEN. Once merged, add this badge to the top of README.md (after the title):
[](https://github.com/punkpeye/awesome-mcp-servers). Check status:gh pr view 2162 --repo punkpeye/awesome-mcp-servers --json state - MCP registry publisher: The CLI is now
mcp-publisher(homebrew binary), NOT the old@anthropic-ai/mcp-publishernpm package. Update step 6 in Publishing Checklist above.
Security Notes
.mcpregistry_*tokens are in.gitignore— never commit these.envcontains API keys — never commit- Tailwind extractor intentionally avoids code execution (no eval, no new Function)
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.
- 10d ago First seen · 36 lines · 556 tokens per session scan A 0acc432e1db9
design-token-bridge-mcp CLAUDE.md is an instructions file published in the GitHub repository kenneives/design-token-bridge-mcp (5 stars, last pushed 23d ago), licensed MIT. It adds 556 tokens to every session, about $0.0028 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-31.
Other instructions, from other repositories
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.
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).
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.
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).
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.