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 od-plugin-contribute-open-designgit 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/od-plugin-contribute-open-design)<a href="https://agentmods.dev/skills/nexu-io/open-design/od-plugin-contribute-open-design"><img src="https://agentmods.dev/badge/skills/nexu-io/open-design/od-plugin-contribute-open-design/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/nexu-io/open-design/od-plugin-contribute-open-design"><img src="https://agentmods.dev/badge/skills/nexu-io/open-design/od-plugin-contribute-open-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Data Exfiltration · line 23 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00027 | $0.00312 |
| Opus 5 | $0.00014 | $0.00156 |
| Sonnet 5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade B, and why
od-plugin-contribute-open-design scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
`curl -sS -X POST "$OD_DAEMON_URL/api/projects/$OD_PROJECT_ID/plugins/contribute-open-design" -H 'content-type: application/json' -d '{"path":"<plugin_context_path>"}'` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -sS -X POST "$OD_DAEMON_URL/api/projects/$OD_PROJECT_ID/plugins/contribute-open-design" -H 'content-type: application/json' -d '{"path":"<plugin_context_path>"}'` What it actually says
Contribute Plugin to OpenDesign
Use this workflow when the active project contains a copied plugin folder and the user wants to propose it for the OpenDesign community catalog.
Workflow
- Read the active plugin inputs.
plugin_context_pathis the copied plugin folder relative to the project working directory. - Inspect the copied plugin's manifest, skill instructions, examples, and compatibility metadata.
- Call the local daemon endpoint instead of hand-rolling GitHub commands:
curl -sS -X POST "$OD_DAEMON_URL/api/projects/$OD_PROJECT_ID/plugins/contribute-open-design" -H 'content-type: application/json' -d '{"path":"<plugin_context_path>"}' - Read the JSON response. If
okis true, report the PR URL, branch name when present in the log, and any useful validation summary. - If the endpoint fails, report its
message,code, and useful log lines. When authentication is missing, tell the user to rungh auth login --hostname github.com.
Keep the pull request focused. Do not modify unrelated OpenDesign files unless a manifest validation issue requires a tiny supporting change.
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.
- 6d ago First seen · 28 lines · 27 tokens per session scan B 362f139f3e60
od-plugin-contribute-open-design is a skill published in the GitHub repository nexu-io/open-design (95,309 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 312 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
repo-map
Use when locating a registered or related local repository, or when discovering commands registered through repo-map. Do not use for source-tree, symbol, or architecture mapping.
memtrace-evolution
Trace source-code change history from Memtrace's symbol-level temporal memory. Use when the user asks about change history, recent modifications, what changed since a date, symbol timeline, evolution, unexpected changes, or incident timelines. Do not use git log, git diff, Grep, or manual file search to reconstruct…
memtrace-cochange
Find files that historically co-change with a target symbol or file, ranked by co-occurrence across git episodes. Use when the user asks about historical coupling, co-change, what changes with this, hidden dependencies, or what else needs to move for source code. Do not use git log, git diff, Grep, or manual file…
memtrace-episode-replay
Replay the graph diff of one episode — a single git commit or working-tree save — to inspect what it changed: added/modified/removed symbols and edges. Use when the user asks what one commit or save changed in the graph, why code looks this way, or wants to inspect implementation attempts, reversions, past reasoning…
memtrace-daily
Orient at the start of a coding session, review what recently changed in a repository, and self-audit after completing work. Use when the user wants the daily briefing (what changed in the last 24h with complexity deltas), hotspots (complexity × churn refactor priorities), or a session review (clean/review/risky…
ship-task
Take an AI Atelie task — issue, ticket, or ad-hoc ask — all the way from description to merged-ready PR. Use whenever the user says "implement X and ship it", "work on issue.