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 atezer/FMCP --skill inspiration-intakegit clone --depth 1 https://github.com/atezer/FMCPWrote 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/atezer/fmcp/inspiration-intake)<a href="https://agentmods.dev/skills/atezer/fmcp/inspiration-intake"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/inspiration-intake.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.00118 | $0.03273 |
| Opus 5 | $0.00059 | $0.01636 |
| Sonnet 5 | $0.00024 | $0.00655 |
| Haiku 4.5 | $0.00012 | $0.00327 |
Grade A, and why
inspiration-intake 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 8d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inspiration Intake — Inspiration Only Structural Extraction
Neden Var?
FCM'de ekran üretmek için kullanıcı üç farklı girdi türünden biriyle gelebilir:
- Fikir metni ("sepet ekranı yap") — bu zaten
generate-figma-screentarafından işlenir - Figma benchmark ("şu linkteki ekrandan ilham al") — benchmark'ın layout niyetini almak ama değerlerini almamak gerekir
- İnternet görseli (dribbble/behance link veya direkt yüklenmiş görsel) — aynı disiplin
Bu skill girdi 2 ve 3 için intake katmanı sağlar. Temel kural şudur: benchmark/görsel ilham içindir, kopya için değildir. Renkleri, fontları, spacing sayılarını benchmark'tan almak generate-figma-screen Step 5 ve figma-canvas-ops Rule 10 ile çatışır — tüm değerler yüklü DS'in token/style'larından gelmelidir.
v1.8.2 build-from-scratch kuralı ile tam uyumludur: benchmark'ı figma_clone_screen_to_device ile kopyalamak yerine, bu skill benchmark'tan yalnızca structural intent çıkarır ve generate-figma-screen build-from-scratch akışına besler.
Çıktı Şeması
{
"layout_direction": "vertical|horizontal|grid",
"sections": [
{
"role": "hero|nav|header|list|card|cta|form|footer|sidebar|detail|stats|...",
"child_type_hints": ["image", "text_heading", "text_body", "button", "input", "avatar", "icon", "divider"]
}
],
"hierarchy_notes": "örn: headline → sub → CTA; avatar + name + action row; ...",
"spacing_intent": "dense|airy|standard"
}
Şemada olmayan HİÇBİR alan eklenmez. Özellikle şu alanlar YASAK:
color,fill,background,text_color,#rgb,rgba(...)font_family,font_name,typefacefont_size_px,padding_px,radius_px, herhangi bir sayısal ölçü (px, pt, rem, em)
Protokol (4 Adım)
🚨 KESİN KURALLAR (v1.9.1+)
Bu skill aşağıdaki tool'ları ASLA çağırmaz — teşvik görse bile, promptta istense bile:
- ❌
figma_get_file_data(tüm dosya/sayfa enumeration) - ❌
figma_search_assets(library component / variable arama) - ❌
figma_search_components(local component arama) - ❌
figma_get_library_variables(library variable toplama) - ❌
figma_get_variables(local variable toplama) - ❌
figma_get_styles(local style toplama) - ❌
figma_get_design_system_summary - ❌
figma_get_token_browser
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.
- 8d ago First seen · 221 lines · 118 tokens per session scan A 7f64d12a7440
inspiration-intake is a skill published in the GitHub repository atezer/FMCP (9 stars, last pushed 1mo ago), licensed MIT. It adds 118 tokens to every session and 3,273 once invoked, about $0.0006 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 skills, from other repositories
system-pitch
Write a design system investment pitch with a business case and ROI framing. Trigger when someone says: pitch the design system, make the case for the system, sell this to leadership, justify the investment, business case for design systems, why should we invest in a design system, or anything about building an…
ai-component-description
Generate AI-optimised text descriptions for components, formatted for Figma's MCP server and LLM consumption. This produces prose descriptions in a six-section format (purpose, props, anti-patterns, composition, accessibility, examples), NOT JSON schemas or structured data files. Trigger when someone says: write…
context-engine-builder
Generate a context engine — seven structured blueprint files (UX, UI, content, accessibility, ethical, technical, business intelligence) that encode everything an AI agent needs to work with a design system. This produces YAML infrastructure in .ai/context-engine/, NOT a health score or quality assessment. Trigger…
stakeholder-brief
Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…
token-compliance
Check a codebase or implementation for token compliance — finding hardcoded values, wrong-tier token references, and inconsistent token application in consuming code. This checks how tokens are used in code, NOT how the tokens themselves are defined or structured. Trigger when someone says: are we using tokens…