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.
git clone --depth 1 https://github.com/HermeticOrmus/LibreEmbed-Claude-CodeWrote 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/hermeticormus/libreembed-claude-code/debug-trace)<a href="https://agentmods.dev/plugins/hermeticormus/libreembed-claude-code/debug-trace"><img src="https://agentmods.dev/badge/plugins/hermeticormus/libreembed-claude-code/debug-trace/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/plugins/hermeticormus/libreembed-claude-code/debug-trace"><img src="https://agentmods.dev/badge/plugins/hermeticormus/libreembed-claude-code/debug-trace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
debug-trace 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 15d 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": "debug-trace",
"version": "1.0.0",
"description": "On-target debugging for Cortex-M: SWD and JTAG probes, HardFault decoding, GDB, ITM and SWO trace, and DWT timing.",
"author": {
"name": "Diego Bodart",
"url": "https://github.com/HermeticOrmus"
},
"homepage": "https://github.com/HermeticOrmus/LibreEmbed-Claude-Code",
"repository": "https://github.com/HermeticOrmus/LibreEmbed-Claude-Code",
"license": "MIT",
"keywords": [
"embedded",
"debugging",
"swd",
"jtag",
"openocd",
"gdb",
"trace"
]
}
What it installs
The manifest is a name and a version. 1 skill, 1 command, 1 agent travel with it, and installing the plugin installs all of them — 196 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.
- 15d ago First seen · 22 lines scan A bf552c7716cb
debug-trace is a plugin published in the GitHub repository HermeticOrmus/LibreEmbed-Claude-Code (50 stars, last pushed 6d 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-10-01.
Other plugins, from other repositories
jlink-mcp
Embedded debugging on real hardware through SEGGER J-Link, OpenOCD, and Black Magic probes. Skills for crash diagnosis, hangs, peripheral inspection, and RTT — including loading ELF symbols for source-level backtraces and SVD files for named peripheral fields.
embedded-debugger
Embedded debugger workflow for probe-rs targets. Provides a CLI-first skill and optional MCP server for probe discovery, target checks, flashing, memory access, and RTT workflows.
esp32-chips
Chip-level ESP-IDF capability references for the Espressif SoCs behind M5Stack boards: classic ESP32 (Xtensa LX6), ESP32-S3 (Xtensa LX7), ESP32-C6 (RISC-V, WiFi 6 + Thread/Zigbee), and ESP32-P4 (RISC-V, MIPI-DSI/CSI, no radio). Covers peripherals, sleep modes and ULP/LP coprocessors, memory and PSRAM config, USB…
membrowse
MemBrowse memory tracking integration for embedded firmware projects. Automatically sets up GitHub workflows for RAM/Flash analysis.
sticky-device
Hardware, firmware, and publishing context for the Seeed Studio reTerminal Sticky (ESP32-S3 e-ink device).
embedded-debug
Embedded Linux DUT serial debugger: boot-log capture, U-Boot control, kernel-crash detection, relay reset, StageLearner self-learning, RFC 2217 dynamic baud-rate control (serialsetbaud). Provides an MCP server (debug-console-mcp) plus Senior hook for auto-start, statusline blocking and raw-serial enforcement.