OpenDesign is an open-source, local-first desktop app that lets coding agents create prototypes, dashboards, slide decks, images, video, and design systems as exportable files. It is used by people working with agent runtimes such as Claude Code, Codex, Cursor, and DeepSeek Harness. The catalogue add-ons extend the OpenDesign workflow with skills, instructions, commands, and plugins.
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 nexu-io/open-design --skill handoffgit clone --depth 1 https://github.com/nexu-io/open-designWrote 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/nexu-io/open-design/handoff)<a href="https://agentmods.dev/skills/nexu-io/open-design/handoff"><img src="https://agentmods.dev/badge/skills/nexu-io/open-design/handoff.svg" alt="Measured on agentmods" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00035 | $0.00536 |
| Opus 5 | $0.00017 | $0.00268 |
| Sonnet 5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
handoff 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 4d 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.
What it actually says
Handoff
Spec §11.5.1 / §21.5: an OD run isn't done when the artifact
exists — it's done when the artifact reaches the surface the user
will keep iterating on. This atom is the "push it somewhere"
stage. It's the natural counterpart to diff-review.
Inputs
- The accepted artifact set (after
diff-reviewresolved withdecision: 'accept' | 'partial'). - The export target (one of the
surfaceenum values fromArtifactManifest.exportTargets[].surface).
Surfaces
| surface | typical follow-on |
|---|---|
cli |
the user runs od files read against the project; no extra push |
desktop |
open the project in the OD desktop app |
web |
publish to the public marketplace via spec §13's od:// deep link |
docker |
wrap the artifact into a self-contained container (calls the §15.4 image) |
github |
open a PR via od plugin publish --to <catalog> |
figma |
round-trip back into the figma-migration source file |
code-agent |
hand off to Cursor / Claude Code / Codex sitting on top of the project cwd |
Output
Updates ArtifactManifest.exportTargets[] with a row per push,
appending — never replacing — so the artifact's distribution
history stays append-only.
Convergence
The atom completes when at least one exportTargets[] entry
matches the user's intent or the user explicitly skipped via the
confirmation GenUI surface.
Anti-patterns the prompt fragment forbids
- Pushing the artifact to a surface that wasn't on the user's intent list.
- Mutating
sourcePluginSnapshotId(it's immutable; the export trail is additive). - Treating
figmaas a no-op when the user's source was a Figma file — round-trip is the whole point of the figma-migration scenario.
Status
Implemented by the daemon runner in
apps/daemon/src/plugins/atoms/handoff.ts. It records provenance,
handoffKind, and export targets, then persists the updated artifact
manifest.
What ships with it
1 file 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.
- 4d ago First seen · 63 lines · 35 tokens per session scan A 6d3bade7d4ae
handoff is a skill published in the GitHub repository nexu-io/open-design (94,527 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 536 once invoked, about $0.0002 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
flowai-team-dashboard
A team-management dashboard layout with tabs for members, team details, and activity logs, plus charts and data export.
kanban-board
A Kanban board is a visual task list with columns for stages such as To do, In progress, In review, and Done. It can show filters, labels, due dates, assignees, comments, and swimlanes that group cards.
weekly-update
A six-to-eight-page horizontal team update presentation covering completed work, current work, blockers, metrics, requests, and thanks.
meeting-notes
A meeting-notes layout that records the meeting title, attendees, agenda, decisions, action items, owners, deadlines, status, and next meeting. Action items are tasks agreed during the meeting.
team-okrs
An OKR tracking page for a quarter. OKRs, or objectives and key results, are goals paired with measurable results.
memtrace-fleet-first
Coordinate fleets of coding agents sharing one repo+branch: publish typed intents, classify edit episodes, and resolve conflicts before they collide. Use FIRST when multiple agents work the same repo+branch, before reading/planning/editing, when joining a fleet or handing work off, and when the user says two agents…