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 J-StaR-Films-Studios/VibeCode-Protocol-Suite --skill figmagit clone --depth 1 https://github.com/J-StaR-Films-Studios/VibeCode-Protocol-SuiteWrote 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/j-star-films-studios/vibecode-protocol-suite/figma)<a href="https://agentmods.dev/skills/j-star-films-studios/vibecode-protocol-suite/figma"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/figma/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/j-star-films-studios/vibecode-protocol-suite/figma"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/figma.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, 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 24 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.
- medium Excessive Agency · line 34 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium MCP Rug Pull · line 80 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 88 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00076 | $0.02974 |
| Opus 5 | $0.00038 | $0.01487 |
| Sonnet 5 | $0.00015 | $0.00595 |
| Haiku 4.5 | $0.00008 | $0.00297 |
Grade A, and why
figma 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 6d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma → HyperFrames
Bring the user's Figma work into a composition. Split by capability (design spec §2):
| Phase | What | Transport | Surface |
|---|---|---|---|
| 1 | Static assets | REST | hyperframes figma asset |
| 2 | Brand tokens/styles | REST | hyperframes figma tokens |
| 3 | Components → HTML | REST | hyperframes figma component |
| 4 | Motion → GSAP | MCP only | you, via get_motion_context |
| 5 | Shaders | MCP only / manual export | you |
REST is used wherever it can be (usable at volume, headless); MCP only where Figma exposes no REST equivalent (motion, shaders). Every path freezes assets locally so renders stay deterministic. Storyboard animatics compose Phase-1 asset exports (REST) with agent-driven timeline assembly — no MCP needed. Existing frozen assets, manifest records, and bindings are unaffected by routing changes — the split only changes which credential the next import uses.
Auth — two credentials, scoped
Preflight — before the first CLI call, check a token exists: shell env ([ -n "$FIGMA_TOKEN" ]) or the project .env (the CLI auto-loads it — a .env entry counts as configured). If neither, do NOT run the command to harvest the error — walk the user through the one-time setup first, then stop and wait:
- figma.com/settings → Security → Personal access tokens → Generate new token.
- Scopes — read-only is all this integration ever needs (it never writes to Figma): File content: Read-only + File metadata: Read-only. Optionally Variables: Read-only for brand variables — that scope only works on Figma Enterprise; without it
tokensdegrades to published styles automatically (expected behavior, not an error — say so). export FIGMA_TOKEN="figd_…"— and suggest persisting it (shell profile or project.env) so no future session repeats this.
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.
- 6d ago First seen · 122 lines · 76 tokens per session scan A 51cc527e692f
figma is a skill published in the GitHub repository J-StaR-Films-Studios/VibeCode-Protocol-Suite (24 stars, last pushed 5d ago), licensed ISC. It adds 76 tokens to every session and 2,974 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-09-03.
Other skills, from other repositories
ip-diagram-creator
A Chinese-language visual-content skill that turns user-provided personal material into a reusable simple hand-drawn character and content illustrations. It can guide prompts or create images when suitable image tools are available.
gc-muted-zine-poster-v0-1
Generate Muted Zine Poster v0.1 poetic paper-poster prompts and the matching generated image. Use when the user gives a theme, sentence, object, mood, article idea, photo, or content brief and wants a quiet Japanese/Korean zine-like editorial poster with large negative space, aged paper texture, experimental…
character-asset
A reference-image workflow for designing consistent fictional characters. It records appearance, materials, lighting, proportions, viewpoints, variations, and checks in an asset contract for later image or video work.
cyberpunk-design
A visual-design guide for creating cyberpunk-style scenes, using defined camera choices, neon colours, lighting, space, movement, materials, and continuity rules.
horror-design
A visual design preset for horror scenes in films, games, or other visual work. It defines observable choices for camera shots, colors, lighting, spaces, movement, materials, and continuity.
romance-design
A visual design preset for romance stories about love, intimacy, warmth, and confession. It defines camera choices, colours, spaces, movement, materials, and continuity rules.