embedded-workbench-dev

A development marketplace containing the Embedded Workbench plugin. A plugin marketplace is a package listing that tells the coding tool where to find and install an add-on.

In plain words
What is it for?
Use it as a marketplace definition while developing or distributing the Embedded Workbench plugin. The listing identifies the plugin, its version, owner, and source location.
Why use it?
It provides the distribution entry for the Embedded Workbench plugin instead of being the firmware toolkit itself. This separates the plugin’s development listing from the plugin it offers.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add AmethystLuna/embedded-workbench
agentmods
npx agentmods add plugins/amethystluna/embedded-workbench/marketplace
Clone the repo
git clone --depth 1 https://github.com/AmethystLuna/embedded-workbench

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

embedded-workbench-dev 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 2d 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.

.claude-plugin/marketplace.json · 16 lines

What it actually says

{
  "name": "embedded-workbench-dev",
  "description": "Development marketplace for Embedded Workbench plugin",
  "owner": {
    "name": "Amethyst Luna"
  },
  "plugins": [
    {
      "name": "embedded-workbench",
      "description": "Your embedded firmware toolkit in Claude Code | Claude Code 嵌入式固件工具箱 — 4 agents, 7 skills, battle-tested on real Cortex-M projects.",
      "version": "0.8.1",
      "source": "./"
    }
  ]
}
Files

What ships with it

1 file beside marketplace.json 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.

Changes

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.

  1. 2d ago First seen · 16 lines scan A a822e788ad06

Subscribe to this mod's changes

embedded-workbench-dev is a plugin published in the GitHub repository AmethystLuna/embedded-workbench (5 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.