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/P47Phoenix/Claude-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/p47phoenix/claude-plugins/hardware-team)<a href="https://agentmods.dev/plugins/p47phoenix/claude-plugins/hardware-team"><img src="https://agentmods.dev/badge/plugins/p47phoenix/claude-plugins/hardware-team/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/p47phoenix/claude-plugins/hardware-team"><img src="https://agentmods.dev/badge/plugins/p47phoenix/claude-plugins/hardware-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hardware-team 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": "hardware-team",
"description": "Hardware delivery team with 8-stage pipeline orchestrator for structured hardware product development. Coordinates 6 hardware roles (HW Product Owner, Electrical Engineer, PCB Layout Engineer, Manufacturing Engineer, Compliance Engineer, Test Engineer) through concept-to-production pipeline. Consumes kicad-happy skills for component sourcing, fabrication, analysis, and documentation.",
"source": "./",
"strict": false,
"skills": [
"./hardware-team/skills/hardware-flow",
"./hardware-team/skills/hw-product-owner",
"./hardware-team/skills/electrical-engineer",
"./hardware-team/skills/pcb-layout-engineer",
"./hardware-team/skills/manufacturing-engineer",
"./hardware-team/skills/compliance-engineer",
"./hardware-team/skills/test-engineer"
]
}What it installs
The manifest is a name and a version. 7 skills travel with it, and installing the plugin installs all of them — 325 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#hardware-team 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.
- 1mo ago First seen · 15 lines scan A 97c3192a52a1
hardware-team is a plugin published in the GitHub repository P47Phoenix/Claude-Plugins (2 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-09-03.
Other plugins, from other repositories
print-hive-farm-crew
Marketplace pack of Print Hive farm role agents: Foreman, Trendy, Spool, Nest, Wrench, and Counter. Use when an operator wants a print-farm crew on Cursor or Grok Bot — onboard MCP, scout models, manage filament, slice, maintain printers, and clear channel orders — with farm-safe confirmations for buys, parts…
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills own folder layout and templates; /obw:pm splits a spec into blocking tickets; /issue is a Claude Mod pane that lists a view of the project's dashboard, draws Mermaid as text diagrams, and can open a card in the browser through viz.…
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested, stacked PR or MR with agents.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.