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 respira-press/agent-skills-wordpress --skill figma-to-bricksgit clone --depth 1 https://github.com/respira-press/agent-skills-wordpressWrote 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/respira-press/agent-skills-wordpress/figma-to-bricks)<a href="https://agentmods.dev/skills/respira-press/agent-skills-wordpress/figma-to-bricks"><img src="https://agentmods.dev/badge/skills/respira-press/agent-skills-wordpress/figma-to-bricks/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/skills/respira-press/agent-skills-wordpress/figma-to-bricks"><img src="https://agentmods.dev/badge/skills/respira-press/agent-skills-wordpress/figma-to-bricks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 46 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00083 | $0.01669 |
| Opus 5 | $0.00042 | $0.00834 |
| Sonnet 5 | $0.00017 | $0.00334 |
| Haiku 4.5 | $0.00008 | $0.00167 |
Grade A, and why
figma-to-bricks 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 11d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma to Bricks
Rebuilds a Figma frame as a real, editable Bricks page. Reads the Figma node tree (layers, auto-layout, text, colors, images), maps each node to its closest Bricks element, scaffolds BEM global classes so styling stays reusable instead of inline, imports the frame's palette into the Bricks color system, and writes to a draft so nothing live is touched.
What This Skill Does
Figma stores a tree of nodes with auto-layout; Bricks stores a flat element list with parent/child references, global classes, and a real design-token system. This skill maps between them and leans on what makes Bricks special: the styling lands in reusable global classes and the Bricks palette, not in per-element value copies.
Handles:
- Frames and auto-layout →
section/container/blockwith flex direction, gap, padding and alignment carried across - Text nodes →
heading(level inferred from font size) ortext-basic/rich text - Rectangles/ellipses with image fills →
image; plain shapes → styled containers; lines →divider - Repeated patterns by layer name + structure: FAQ stacks →
accordion, image rows →image-galleryorcarousel, number+label pairs →counter, platform icon rows →icongroups - Typography and colors as BEM global classes (
respira_bricks_scaffold_bem) referencing tokens, not inline values - The frame's palette imported into the Bricks color palette (
respira_bricks_import_design_tokens/respira_update_bricks_color_palette) so later edits stay on-brand - ACSS awareness: when Automatic.css is installed (
respira_bricks_detect_acss), map spacing/typography onto ACSS utility classes instead of raw values - Image fills downloaded from Figma and sideloaded into the media library
Preserves: text content, links and media; layout structure and nesting; visual styling as closely as Bricks' rendering allows — with the styling held in classes and tokens.
What This Skill Does NOT Do
- Pixel-perfect recreation — different rendering engines; expect light manual fine-tuning
- Figma components with overrides / variants — flattened to visible content and flagged
- Prototyping and interactions — skipped
- Complex vector art, masks, blend modes — flattened to images where possible, otherwise flagged
- Auto-generated responsive breakpoints — desktop-first; tablet/mobile passes are manual unless the file has explicit responsive frames
- Query loops / dynamic data — this builds static page content; wiring dynamic sources is a follow-up
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.
- 11d ago First seen · 99 lines · 83 tokens per session scan A 02568221a033
figma-to-bricks is a skill published in the GitHub repository respira-press/agent-skills-wordpress (43 stars, last pushed 2d ago), licensed MIT. It adds 83 tokens to every session and 1,669 once invoked, about $0.0004 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
data-display-and-selection
Complex data deserves multiple view modes — grid, list, table — chosen by the user based on their task. Row and item selection should use large hit areas (the whole row or card, not just a checkbox). Selected state is communicated through a subtle background colour shift. Mass actions appear when items are selected.…
information-architecture
In large applications, information architecture determines whether users can find, understand, and act on data. Naming matters. The UI should mirror the data model and signal how data can be transformed. Dangerous or irreversible changes always require a confirm dialog. Use when designing navigation, naming entities…
brand-visual-language
A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens…
generate-ui-from-brand
Pipeline skill — turns a URL or DESIGN.md into a concrete UI structure with decisions already made. Extracts live design tokens, normalizes them into a semantic system, applies UX principles, and outputs an actionable UI spec. Use when building UI for an existing brand from scratch, auditing a design system, or…
loading-states-and-perceived-performance
Manage user expectations during wait times with appropriate loading states — from simple spinners to complex skeleton screens and staggered animations. Perceived performance is often more important than actual load time. Use when designing data-heavy components, handling API calls, building hero sections, or improving…
micro-interactions
Micro-interactions are small, purposeful animations and responses that reward the user and make the interface feel alive — an animated icon, a satisfying toggle, a subtle reveal. Borrowed from the natural world, they add delight without distraction. Use when designing interactive components, success states, toggles…