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.
/plugin marketplace add AmethystLuna/embedded-workbenchnpx agentmods add plugins/amethystluna/embedded-workbench/embedded-workbenchgit clone --depth 1 https://github.com/AmethystLuna/embedded-workbenchGrade A, and why
embedded-workbench 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.
What it actually says
{
"name": "embedded-workbench",
"version": "0.8.1",
"description": "Embedded C/C++ development toolbox | 嵌入式 C/C++ 开发工具箱 — 4 agents, 7 skills: FreeRTOS, Keil MDK, ARMCLANG, HardFault triage, state machines, architecture, LVGL patterns.",
"author": {
"name": "Amethyst Luna",
"url": "https://github.com/AmethystLuna"
},
"homepage": "https://github.com/AmethystLuna/embedded-workbench",
"repository": "https://github.com/AmethystLuna/embedded-workbench",
"license": "MIT",
"keywords": ["embedded", "firmware", "c", "cpp", "freertos", "debugging", "keil", "armclang", "cortex-m", "hardfault", "state-machine", "lvgl", "architecture"]
}
What ships with it
1 file beside plugin.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.
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.
- 2d ago First seen · 14 lines scan A cb77f2e491cb
embedded-workbench 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.
Other plugins, from other repositories
better-harness
Better Harness plugins for AI delivery readiness.
better-harness
Build an AI-ready engineering system for safe coding-agent delivery and continuous software improvement.
starrykit
Create editable presentations, posters, social graphics, art, and visual design documents with StarryKit.
starrykit-plugin
Create editable presentations, posters, social graphics, art, and visual design documents from prompts and references.
yegor256
Claude Code plugins maintained by Yegor Bugayenko.
hypergrok
Turn your agent into a Hyperliquid trading desk: seven specialist roles with full system prompts and sixteen skills for research, risk, execution and review.