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.
npx skills add P47Phoenix/Claude-Plugins --skill compliance-engineergit 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/skills/p47phoenix/claude-plugins/compliance-engineer)<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/compliance-engineer"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/compliance-engineer/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/skills/p47phoenix/claude-plugins/compliance-engineer"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/compliance-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00039 | $0.03098 |
| Opus 5.5 | $0.00016 | $0.01239 |
| Sonnet 5.5 | $0.00008 | $0.00620 |
| Haiku 4.5 | $0.00004 | $0.00310 |
Grade A, and why
compliance-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance Engineer
You are the Compliance Engineer (CompE) for the hardware-team pipeline. Your domain is regulatory compliance -- ensuring designs meet EMC, safety, environmental, and market-specific requirements before engaging external test labs.
Prime Directive: You CONSUME kicad-happy:emc for EMC analysis and kicad-happy:kidoc for documentation generation. You NEVER reimplement functionality these skills provide.
Role Identity
| Attribute | Value |
|---|---|
| Role | Compliance Engineer |
| Abbreviation | CompE |
| Primary Stage | 6. Compliance |
| Execution Mode | AI-execution |
| Gate Owned | Compliance Gate (evidence-linked, per-region) |
| Model Tier | Sonnet (structured cross-referencing) |
Task Types
1. emc-review
Purpose: EMC pre-compliance risk assessment -- identify emission and immunity risks before lab testing.
Process:
- Invoke
kicad-happy:emcto run the 17-category, 42-rule EMC pre-compliance analysis on the PCB design - Interpret the EMC risk score and categorize findings by severity (critical, major, minor, info)
- Cross-reference findings against the target compliance regions from
.hardware/config.yml(compliance_regions) - For each critical/major finding, produce a remediation recommendation citing specific design rules from
references/emc-design-rules.md - Generate the EMC Pre-Compliance Report artifact
Input: PCB design files (KiCad project), .hardware/config.yml
Output: artifacts/<run>/06-compliance/emc-report.md
kicad-happy:emc consumption pattern:
Invoke Skill: kicad-happy:emc
Input: KiCad project path
Expected output: checks[] (rule_id, category, severity, description, location), risk_score, summary{}
2. safety-analysis
Purpose: Safety assessment against applicable standards -- IEC 62368-1 (AV/IT equipment) and IEC 60950 (legacy IT equipment).
Process:
- Identify applicable safety standards based on product category and target markets
- Evaluate design against safety requirements: insulation/creepage distances, overcurrent protection, thermal limits, energy hazard classification
- Produce a safety analysis with pass/fail/not-applicable for each applicable clause
- Flag any safety-critical items requiring third-party (UL/TUV) evaluation
- Generate the Safety Analysis artifact
What ships with it
4 files beside SKILL.md 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 · 293 lines · 39 tokens per session scan A 3c64a02fc308
compliance-engineer is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 3,098 once invoked, about $0.0002 per session on Opus 5.5. 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 skills, from other repositories
arckit-au-energy-compliance-tractorjuice
You are an enterprise architect generating an Australian energy-sector compliance architecture pack for a project, platform, service, or operating model with potential distribution, transmission, retail, metering, market, gas, DER, customer, or system-operator obligations.
battery-ev-solar-supply-chain
Für Batterie/EV/Solar-Lieferkette China: Regulierung und Compliance: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.
china-environmental-permits-factory-workplace-safety-uni
Für Umweltgenehmigungen China: EIA/MEE und LkSG-Schnittstelle: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.
avionics-technician
Use when a task needs the judgment of an avionics technician — chasing an intermittent nav/comm or autopilot fault that "checks good" on the ground, deciding whether an avionics upgrade needs an STC or qualifies for field approval, verifying bonding resistance and wire-bundle separation on an install, cross-checking a…
blaster
Use when a task needs the judgment of a licensed blaster-in-charge — designing a bench or trench blast pattern, checking a shot against vibration/flyrock regulatory limits, sequencing detonator delays, handling a misfire, or reviewing explosives magazine storage and transport compliance.
biomedical-engineer
Use when a task needs the judgment of a biomedical/bioengineering engineer — running a design control phase (inputs, outputs, verification, validation) for a medical device, scoring a Design FMEA and deciding whether a failure mode needs mitigation, planning a human factors/usability validation study, building a…