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/hipson47/hipson/figma-code-connect-componentsnpx skills add Hipson47/Hipson --skill figma-code-connect-componentsgit clone --depth 1 https://github.com/Hipson47/HipsonWrote 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/hipson47/hipson/figma-code-connect-components)<a href="https://agentmods.dev/skills/hipson47/hipson/figma-code-connect-components"><img src="https://agentmods.dev/badge/skills/hipson47/hipson/figma-code-connect-components.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 | $0.00081 | $0.04131 |
| Opus 5 | $0.00041 | $0.02065 |
| Sonnet 5 | $0.00016 | $0.00826 |
| Haiku 4.5 | $0.00008 | $0.00413 |
Grade A, and why
figma-code-connect-components 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 3d 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Connect Components
Overview
This skill helps you connect Figma design components to their corresponding code implementations using Figma's Code Connect feature. It analyzes the Figma design structure, searches your codebase for matching components, and establishes mappings that maintain design-code consistency.
Skill Boundaries
- Use this skill for
get_code_connect_suggestions+send_code_connect_mappingsworkflows. - If the task requires writing to the Figma canvas with Plugin API scripts, switch to figma-use.
- If the task is building or updating a full-page screen in Figma from code or a description, switch to figma-generate-design.
- If the task is implementing product code from Figma, switch to figma-implement-design.
Prerequisites
- Figma MCP server must be connected and accessible
- User must provide a Figma URL with node ID:
https://figma.com/design/:fileKey/:fileName?node-id=1-2- IMPORTANT: The Figma URL must include the
node-idparameter. Code Connect mapping will fail without it.
- IMPORTANT: The Figma URL must include the
- OR when using
figma-desktopMCP: User can select a node directly in the Figma desktop app (no URL required) - IMPORTANT: The Figma component must be published to a team library. Code Connect only works with published components or component sets.
- IMPORTANT: Code Connect is only available on Organization and Enterprise plans.
- Access to the project codebase for component scanning
Required Workflow
Follow these steps in order. Do not skip steps.
Step 1: Get Code Connect Suggestions
Call get_code_connect_suggestions to identify all unmapped components in a single operation. This tool automatically:
- Fetches component info from the Figma scenegraph
- Identifies published components in the selection
- Checks existing Code Connect mappings and filters out already-connected components
- Returns component names, properties, and thumbnail images for each unmapped component
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 350 lines · 81 tokens per session scan A 0f19edad8aed
figma-code-connect-components is a skill published in the GitHub repository Hipson47/Hipson (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 81 tokens to every session and 4,131 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-31.
Other skills, from other repositories
deploy
Use when shipping a release of Agent Sessions — bumping version, updating CHANGELOG, building, signing, notarizing, publishing appcast, and creating a GitHub release.
release-notes
Use when writing or curating the user-facing release copy for an Agent Sessions release — README "What's New", GitHub release notes, Sparkle release notes, or website/launch copy. Not for the internal CHANGELOG, which stays a full development history.
sc-skill
Capture deterministic macOS screenshots for testing, docs, release notes, and marketing assets. Use when asked to automate app screenshots, batch-generate screenshot sets, standardize window sizing/composition, or choose between Peekaboo and native macOS screenshot tooling.
add-agent-support
Create and ship AgentSessions support for a new or changed local AI agent/provider. Use when adding, reviewing, testing, documenting, or marketing a provider integration, session parser, transcript source, support-matrix entry, verified-version bump, or provider UI surface; drives the full loop from pre-support…
handover
Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".
agent-session-format-check
Verify agent session format compatibility for Agent Sessions. Use when any agent CLI updates, when monitoring flags drift, or when bumping max verified versions (fixtures + docs + tests). Covers session schema, usage/limits tracking, storage backends, and discovery path contracts for all supported agents.