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/w1ne/labwired-coreWrote 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/w1ne/labwired-core/labwired)<a href="https://agentmods.dev/plugins/w1ne/labwired-core/labwired"><img src="https://agentmods.dev/badge/plugins/w1ne/labwired-core/labwired/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/w1ne/labwired-core/labwired"><img src="https://agentmods.dev/badge/plugins/w1ne/labwired-core/labwired.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
labwired 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": "labwired",
"version": "0.1.0",
"description": "Design electronic circuits, simulate and verify embedded firmware, and lay out supported PCBs with LabWired.",
"author": {
"name": "LabWired",
"url": "https://labwired.com"
},
"homepage": "https://labwired.com/mcp.html",
"repository": "https://github.com/w1ne/labwired-core",
"license": "MIT",
"keywords": [
"electronics",
"circuit",
"firmware",
"pcb",
"embedded",
"arduino",
"esp32",
"kicad"
]
}
What it installs
The manifest is a name and a version. 1 skill, 1 MCP server travel with it, and installing the plugin installs all of them — 31 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 · 23 lines scan A e788d1cc5891
labwired is a plugin published in the GitHub repository w1ne/labwired-core (89 stars, last pushed today), 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-11-05.
labwired compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| labwiredw1ne/labwired-core | Plugin | 89 | today | MIT | A | — | Claude Code |
| unifi-networksirkirby/unifi-mcp | Plugin | 1.0k | today | MIT | A | — | Claude Code |
| unifi-protectsirkirby/unifi-mcp | Plugin | 1.0k | today | MIT | A | — | Claude Code |
| unifi-intelligencesirkirby/unifi-mcp | Plugin | 1.0k | today | MIT | A | — | Claude Code |
| android-remote-controldanielealbano/android-remote-control-mcp | Plugin | 785 | yesterday | none | A | — | Claude Code |
| connectwise-controlServosity/msp-skills | Plugin | 70 | today | none | A | — | Claude Code |
| domotzServosity/msp-skills | Plugin | 70 | today | none | A | — | Claude Code |