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 agentmods add skills/atezer/fmcp/ai-handoff-exportnpx skills add atezer/FMCP --skill ai-handoff-exportgit 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/ai-handoff-export)<a href="https://agentmods.dev/skills/atezer/fmcp/ai-handoff-export"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/ai-handoff-export.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.00155 | $0.03482 |
| Opus 5 | $0.00077 | $0.01741 |
| Sonnet 5 | $0.00031 | $0.00696 |
| Haiku 4.5 | $0.00015 | $0.00348 |
Grade A, and why
ai-handoff-export 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 5d 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Handoff Export
Overview
Bu skill, dağınık Figma çıktılarını tek bir teslimat formatında toplar:
HANDOFF_TEMPLATE.md(insan okunur)handoff.manifest.json(makine okunur, schema tabanlı)
Önemli: Tüm veriler plugin bridge üzerinden alınır. Şablon: repo kökünde HANDOFF_TEMPLATE.md; şema: docs/handoff.manifest.schema.json.
F-MCP skill koordinasyonu
- Önce: Tuval DS uyumu için isteğe bağlı audit-figma-design-system / apply-figma-design-system; token isimleri için design-token-pipeline ile uyumlu manifest.
- Sonra: implement-design ana tüketici; code-design-mapper özetini manifest’e işleyebilirsin.
- PO/PM akışı: Teknik olmayan ekran özeti için figma-screen-analyzer; değişiklik etkisi için ds-impact-analysis
Required Workflow
Step 1: Plugin Bağlantısını Doğrula
figma_get_status()
Step 2: Hedef node'ları netleştir
- Kullanıcı URL verdiyse
node-iddeğerini ayıkla. - Node belirsizse
figma_get_file_data(depth=1)ile kapsam çıkar.
Step 3: Design context topla
figma_get_design_context çağrısı:
includeLayout=trueincludeVisual=trueincludeTypography=trueincludeCodeReady=truedepth=2
Step 4: Token ve component reuse özeti çıkar
figma_get_variablesfigma_search_components- gerekiyorsa
figma_get_component_for_development
Step 4.5: Prototip Akış Diyagramı (v1.9.9+)
Ekran prototip bağlantıları içeriyorsa handoff'a "Prototip Akışı" bölümü ekle:
const proto = await figma_get_prototype_connections({ pageScope: true });
Manifest'e prototypeFlow anahtarı olarak yaz:
{
"prototypeFlow": {
"startingPoints": [{ "nodeId": "...", "name": "Login Akışı" }],
"connections": [
{ "source": "Login/LoginBtn", "destination": "Home", "trigger": "ON_CLICK", "action": "NAVIGATE", "transition": { "type": "SLIDE_IN", "direction": "RIGHT", "duration": 0.3 } }
],
"totalReactions": 12
}
}
HANDOFF_TEMPLATE'e "## Prototip Akışı" bölümü ekle (Mermaid graph TD):
graph TD
Login -->|Giriş Yap - SLIDE_IN/RIGHT 300ms| Home
Login -->|Kayıt Ol - SLIDE_IN/RIGHT 300ms| Register
Login -->|Şifremi Unuttum - SLIDE_IN/RIGHT 300ms| ForgotPassword
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.
- 5d ago First seen · 294 lines · 155 tokens per session scan A 62f88e42b3c4
ai-handoff-export is a skill published in the GitHub repository atezer/FMCP (9 stars, last pushed 1mo ago), licensed MIT. It adds 155 tokens to every session and 3,482 once invoked, about $0.0008 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…
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…
accessibility-per-component
Run an accessibility audit on a specific design system component. Trigger when someone says: accessibility check, a11y audit, WCAG compliance, is this accessible, check accessibility, does this meet WCAG, screen reader support, keyboard navigation check, or anything about auditing the accessibility of a specific…
codemod-generator
Generate codemods (automated code transformation scripts) for design system migrations — token renames, component API changes, prop deprecations, and import path updates. Produces ready-to-run jscodeshift or custom AST transform scripts that safely apply changes across consuming codebases. Trigger when someone says…