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/Ed3Design/ed3design-engineering-bundlesWrote 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/ed3design/ed3design-engineering-bundles/maker-fdm)<a href="https://agentmods.dev/plugins/ed3design/ed3design-engineering-bundles/maker-fdm"><img src="https://agentmods.dev/badge/plugins/ed3design/ed3design-engineering-bundles/maker-fdm/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/ed3design/ed3design-engineering-bundles/maker-fdm"><img src="https://agentmods.dev/badge/plugins/ed3design/ed3design-engineering-bundles/maker-fdm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
maker-fdm 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 1mo 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": "maker-fdm",
"version": "0.1.0",
"description": "Maker disciplines for FDM-printed builds and embedded UI documentation. 2 skills covering Bill-of-Materials validation for multi-component physical builds (≥5 parts) and embedded GUI documentation from source (ESP32/Arduino touchscreens with LovyanGFX, TFT_eSPI, U8g2, LVGL).",
"author": {
"name": "ed3Dworks"
},
"homepage": "https://github.com/Ed3Design/ed3design-engineering-bundles",
"repository": "https://github.com/Ed3Design/ed3design-engineering-bundles",
"license": "MIT",
"keywords": [
"fdm",
"3d-printing",
"maker",
"bom",
"embedded",
"esp32",
"arduino",
"lvgl",
"ed3design"
]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 412 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.
- 1mo ago First seen · 23 lines scan A deaee1b4aabf
maker-fdm is a plugin published in the GitHub repository Ed3Design/ed3design-engineering-bundles (2 stars, last pushed 3mo 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
claude-ros2-skills
ROS 2 Jazzy workflows, scoped evidence handoff, test-result checks and runtime diagnostics.
esp32-cpp
ESP32 firmware review for all variants, FreeRTOS, ESP-IDF/PlatformIO, peripherals, and memory.
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.
jko-claude-plugins marketplace
Claude Code plugin marketplace — Rust, ESP32 C++, Python backend, SwiftUI, dead code detection.
code-craftsmanship
Code quality and software design skills including Clean Code (Robert C. Martin), Refactoring patterns (Martin Fowler), A Philosophy of Software Design (John Ousterhout), The Pragmatic Programmer (Hunt & Thomas), Domain-Driven Design (Eric Evans), Working Effectively with Legacy Code (Michael Feathers), and Google's…