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/p2ergmbh/agentic-coding/figma-validatenpx skills add P2ERGmbH/agentic-coding --skill figma-validategit clone --depth 1 https://github.com/P2ERGmbH/agentic-codingWhat 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 | $0.00034 | $0.01295 |
| Opus 5 | $0.00017 | $0.00647 |
| Sonnet 5 | $0.00007 | $0.00259 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
figma-validate 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 2d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma Design Validation Workflow
This workflow guides you through comparing a live component implementation with its original Figma design frame to ensure pixel-perfect visual consistency and design system compliance.
Trigger
Use this workflow when a user provides a Figma Node URL (e.g., https://www.figma.com/design/.../?node-id=...) and wants to validate that the live React component implementation matches the design frame precisely.
Step-by-Step Validation Loop (Iterative Process)
Step 1: Storybook Entry Setup & Verification
- Locate Storybook Stories: Search for an existing Storybook story file adjacent to the component (e.g.,
[ComponentName].stories.tsx). - Create if Missing: If no story file exists, create a brand-new one containing robust mock data matching the component's expected props.
- Confirm with User: Ask the user to verify that you are targeting the correct Storybook entry by invoking the
ask_user_questiontool.
Step 2: Download Figma Design Image
- Extract Parameters Robustly (MANDATORY):
fileKey: Extract the full alphanumeric segment following/design/,/file/, or/board/. CRITICAL: Modern Figma file keys can be longer than 22 characters (e.g., 23 characters:94ca8NwOFXEnWEcOghyEz2). Do NOT assume a fixed 22-character limit or use fixed{22}regexes; extract the full segment up to the next slash/or question mark?using[a-zA-Z0-9]+.nodeId: Extract from thenode-idquery parameter. CRITICAL: Figma browser URLs represent node IDs with hyphens (e.g.,node-id=16512-15263), but the Figma API and MCP tools REQUIRE a colon (e.g.,16512:15263). Always convert hyphens (-) to colons (:) before passing to any tool or API.
- Fetch S3 Image Link: Call the Figma REST API (
GET https://api.figma.com/v1/images/:file_key?ids=:node_id) or usedownload_figma_imagesvia MCP (using correctfileKeyandnodeIdparameter names). - Download PNG (TASK-SPECIFIC FILENAME): Download the Figma frame crop as a PNG file and save it under
public/example/figma_[component_name_lowercase].png(e.g.public/example/figma_product_card.png). NEVER use generic names likefigma_design.pngto prevent asset conflicts across parallel AI tasks.
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.
- 2d ago First seen · 56 lines · 34 tokens per session scan A 452a378ce785
figma-validate is a skill published in the GitHub repository P2ERGmbH/agentic-coding (9 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 1,295 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…