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 Owl-Listener/designpowers --skill figma-bridgegit clone --depth 1 https://github.com/Owl-Listener/designpowersWrote 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/owl-listener/designpowers/figma-bridge)<a href="https://agentmods.dev/skills/owl-listener/designpowers/figma-bridge"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/figma-bridge.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.00130 | $0.01935 |
| Opus 5 | $0.00065 | $0.00967 |
| Sonnet 5 | $0.00026 | $0.00387 |
| Haiku 4.5 | $0.00013 | $0.00194 |
Grade A, and why
figma-bridge 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma Bridge
Designpowers produces excellent specifications — briefs, principles, layout decisions, token systems, copy. But designers think visually, and a spec is not a thing you can look at and feel. This skill closes the loop: it turns the team's decisions into a visual artefact the designer can see and manipulate, and it pulls existing visual work back into the workflow.
It bridges both directions:
- Code/spec → design ("make it real"): push design-lead's visual decisions, the design system, or the built code into real Figma frames
- Design → code/spec ("read this in"): pull an existing Figma file in as the artefact for
design-review, or as the source fortoken-architecture/design-system-alignment
When Figma isn't available, it degrades gracefully to a clickable HTML prototype — no designer is left without something to look at.
When to Use
- At the screenshot checkpoint (after
design-builder) — give the designer a manipulable artefact, not just a screenshot of code - At handoff — sync the final design into Figma so engineering and design share one source
- In
design-review— when the artefact to review is a Figma file or link, pull it in here - As a design-system source — when the user has a Figma library, extract its tokens/components to seed
token-architectureanddesign-system-alignment - On request — "show me", "put this in Figma", "can I see it", "make it real"
Prerequisite: Detect Figma Availability
Check whether the Figma MCP tools are available in this environment (tools named get_design_context, get_screenshot, use_figma, create_new_file, generate_figma_design, etc.).
- If available: use the Figma direction below.
- If not available: skip to the HTML Prototype Fallback. Do not block the workflow waiting for Figma.
⚠️ Mandatory before any Figma write: load Figma's own usage guidance first — invoke the
/figma-useskill if present, otherwise read theskill://figma/figma-use/SKILL.mdMCP resource. Writing to Figma viause_figmawithout it causes common, hard-to-debug failures. The same applies to/figma-generate-design(capturing a web view),/figma-generate-library(building a design system in Figma), and/figma-code-connect(mapping components). This skill orchestrates when to bridge; those Figma skills govern how to write.
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 · 112 lines · 130 tokens per session scan A 6de282bed7a5
figma-bridge is a skill published in the GitHub repository Owl-Listener/designpowers (243 stars, last pushed 2mo ago), licensed MIT. It adds 130 tokens to every session and 1,935 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-30.
Other skills, from other repositories
accessibility-a11y
Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.
tailwind-shadcn
Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.
anti-slop-frontend
A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that…
frontend-mockup-loop
Plan, build, and iterate UX-friendly frontend mockups via a ground→contract→mockup→test→fix→learn loop, acting as an expert UX designer who grounds every decision in externally documented public design rules (Nielsen heuristics, Laws of UX, WCAG, GOV.UK/USWDS/Material). Uses the bundled servemockup, scoremockup, and…
frontend-mockup-loop-dashboard
Dashboard-specific adapter on the generic frontend-mockup-loop skill: binds the 7-step design loop to pi-agent-dashboard component sources, theme-system tokens, and isolated verification. Use when designing/redesigning any pi-agent-dashboard client surface. Triggers: "design a dashboard screen", "mockup a dashboard…
goga-define-experience
Define the user experience required to achieve the established product goals and solve the identified problem.