design-os-figma-agent SKILL.md skillB
design-os-figma-agent from jangtrinh/design-os-figma-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jangtrinh/design-os-figma-plugin/design-os-figma-agent@v0.1.0Pins v0.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jangtrinh/design-os-figma-plugin
- Path
skills/design-os-figma-agent/SKILL.md- Versions recorded
- 2
- Latest version
- v0.1.0, committed Nov 1, 2026
- First version recorded
- Oct 30, 2026
- Size
- 26,303 bytes
- Repository stars
- 25
- License
- a license file GitHub does not identify
figma-agent — the CLI bridge to the Figma file already open in the designer's Figma desktop app, over a local WebSocket broker. SessionStart MAY have already run figma-agent status --peek and left its result in context (only if the optional install-hook was set up) — if no peek result is visible, run figma-agent status --peek first. When it reports a live connection, use THIS skill — not the DesignAgent MCP or any other Figma bridge — for every request to inspect, read, edit, or check the…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# figma-agent
A thin CLI that talks to the Figma plugin "DESIGN:OS Bridge" through a local
broker (127.0.0.1, ports 9410-9419). One command per invocation; every command prints
exactly one JSON object to stdout and exits 0, or `{error:{code,message}}` and exits 1.
## Connect protocol
1. Check state cheaply first: `figma-agent status --peek`. This never spawns a broker —
it only reads the `/tmp` broker advertisement and, if one is live, asks it one short
question. Idle (no broker, or the plugin not open) is a normal, non-error answer.
2. Only run a real command (`status`, `connect`, `create-frame`, ...) once you need to
act — those DO start a broker on demand if none is running.
3. `status --peek`'s `versionMatch`/`protocolMatch` fields tell you whether the
connected plugin build matches this CLI. `null` means the plugin didn't report a
version (an older bundle) — treat that as unknown, not as a mismatch. Plain `status`
does not compute these fields itself — read them from `--peek`.
4. If nothing is connected, the human's remaining step is opening the plugin panel in
Figma desktop — this CLI cannot do that for them.
…Read the whole file at its exact version.
How to install
mdr add jangtrinh/design-os-figma-plugin/design-os-figma-agent@sha256:33a20739de171362The line at the top of this page pins the label v0.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_sxcjb7e5cgfipjtt)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 30, 2026 and Nov 1, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.1.0 latest | 2026-11-01 | 5ad154f | 26,303 B | B | view · diff |
| v0.1.0 | 2026-10-30 | b863ac1 | 26,310 B | B | view |
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (26303 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
jangtrinh/design-os-figma-plugin · 25 stars · license a license file GitHub does not identify · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_sxcjb7e5cgfipjtt GET https://markdownregistry.com/api/v1/resolve?ref=jangtrinh/design-os-figma-plugin/design-os-figma-agent GET https://markdownregistry.com/api/v1/blob/33a20739de171362d8a44baea849ddd92bdf1cc2ebfcb39e48fde8fc1ea12cde
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.