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 qte77/claude-code-pluginsnpx agentmods add plugins/qte77/claude-code-plugins/embedded-devgit clone --depth 1 https://github.com/qte77/claude-code-pluginsWrote 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/plugins/qte77/claude-code-plugins/embedded-dev)<a href="https://agentmods.dev/plugins/qte77/claude-code-plugins/embedded-dev"><img src="https://agentmods.dev/badge/plugins/qte77/claude-code-plugins/embedded-dev.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
embedded-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 yesterday.
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-dev",
"version": "1.2.3",
"description": "Embedded firmware development with CE/FCC compliance, ESP-IDF/PlatformIO, requirement traceability, and KiCad PCB auditing",
"author": {
"name": "Claude Code Utils Contributors"
},
"keywords": [
"embedded",
"firmware",
"esp-idf",
"platformio",
"compliance",
"misra",
"kicad",
"pcb",
"traceability",
"requirements"
]
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 179 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- yesterday First seen · 21 lines scan A de3d117a3017
embedded-dev is a plugin published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 5d ago), licensed Apache-2.0. 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-09-03.
Other plugins, from other repositories
esp32-cpp
Evidence-first ESP32 firmware guidance for hardware, FreeRTOS, memory, peripherals, and field failures.
seam-probe
Generic NDJSON probe for embedded-runtime FFI dylibs and Unix-domain sockets.
esp32-cpp
ESP32 firmware review for all variants, FreeRTOS, ESP-IDF/PlatformIO, peripherals, and memory.
android-kotlin-coroutines
Android development guidance with Kotlin Coroutines and Flow. Structured concurrency, StateFlow/SharedFlow patterns, lifecycle integration, testing with Turbine, and library integrations (Retrofit, Room, WorkManager).
android-analysis
Android APK, AAR, and JAR decompilation and inspection toolkit for analyzing compiled binaries, unpacking libraries, and understanding obfuscated code.
android-kotlin-compose
Android development guidance with Kotlin and Jetpack Compose. MVVM architecture, state management, Navigation, Room, Hilt, and Material3 patterns.