agentmods.dev

checking-compliance

checking-compliance is a skill for Claude Code from qte77/claude-code-plugins. It costs 43 tokens per session (768 once invoked), scanned A, original, Apache-2.0.

A requirements generator for checking whether a new embedded device follows European and US safety, radio, materials, and emissions rules.

In plain words
What is it for?
Use it when starting an embedded product, deciding which CE, FCC, UL, RoHS, or related rules apply, and creating initial SYS-REQ entries.
Why use it?
It turns a device description into a compliance checklist and starting system requirements, so you have a clear list of standards and tests to investigate.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Claude Code.

Part of the embedded-dev plugin — 4 skills shipped together

not rated 3repo yesterday A scan 43 tokens original Apache-2.0

Good fit Use it when starting an embedded product, deciding which CE, FCC, UL, RoHS, or related rules apply, and creating initial SYS-REQ entries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/qte77/claude-code-plugins/checking-compliance
View source ↗ qte77/claude-code-plugins qte77.github.io
Install

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.

Any agent
npx skills add qte77/claude-code-plugins --skill checking-compliance
Clone the repo
git clone --depth 1 https://github.com/qte77/claude-code-plugins

Made for: Claude Code.

Or install embedded-dev, the plugin that ships this one along with the rest of its 4 skills.

Wrote 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.

agentmods badge for checking-compliance

README.md
[![agentmods](https://agentmods.dev/badge/skills/qte77/claude-code-plugins/checking-compliance/github.svg)](https://agentmods.dev/skills/qte77/claude-code-plugins/checking-compliance)
Your own site
<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/checking-compliance"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/checking-compliance/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.

agentmods 80×15 button for checking-compliance

Your own site · 80×15
<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/checking-compliance"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/checking-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 768 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.00768
Opus 5.5 $0.00017 $0.00307
Sonnet 5.5 $0.00009 $0.00154
Haiku 4.5 $0.00004 $0.00077

Measured 1mo ago against content hash 07d04d26d1b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

checking-compliance 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.

plugins/embedded-dev/skills/checking-compliance/SKILL.md · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Compliance Requirements Generation

Target: $ARGUMENTS

Generate a compliance checklist and initial requirements file from applicable regulatory standards based on the device description.

References (MUST READ)

Read these before proceeding:

  • references/compliance-standards.md — Applicable directives, standards, and their scope
  • references/requirement-hierarchy.md — SYS-REQ → PRD-REQ → SW-REQ ID conventions

Workflow

  1. Parse device description — Identify device type, markets (EU/US/both), wireless capability, power source, intended use
  2. Select applicable directives:
    • EU: LVD (2014/35/EU) + EMC (2014/30/EU) + RED (2014/53/EU if wireless) + RoHS + REACH
    • US: UL 62368-1 + FCC Part 15 (+ Part 18 if ISM)
  3. WebSearch for latest standard revisions if unsure about current edition
  4. Generate compliance checklist at docs/compliance-checklist.md with:
    • Each applicable directive/standard
    • Specific clauses relevant to the device type
    • Test requirements (pre-compliance and certification)
  5. Generate requirements file at docs/requirements.md with SYS-REQ entries:
    • One SYS-REQ per applicable standard clause
    • Include norm reference in each entry (e.g., SYS-REQ-001: EN 55032 Class B conducted emission limits)
  6. Output next steps — Explain how to break SYS-REQ into PRD-REQ and SW-REQ, then use implementing-firmware

Output Format

Compliance Checklist

# Compliance Checklist: <Device Name>

## Markets: <EU / US / Both>

### EU Directives
- [ ] LVD 2014/35/EU — IEC 62368-1:2023
  - Clause 5.4: Electrically-caused fire
  - Clause 6.3: Electric shock
- [ ] EMC 2014/30/EU — EN 55032:2015+A1:2020
  ...

Requirements File

# Requirements: <Device Name>

## System Requirements (SYS-REQ)

| ID | Description | Norm Reference | Status |
|----|-------------|----------------|--------|
| SYS-REQ-001 | Device shall meet EN 55032 Class B conducted emission limits | EN 55032:2015+A1:2020 §5 | open |

Read the full file on GitHub · 77 lines

Files

What ships with it

2 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.

Changes

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.

  1. 1mo ago First seen · 77 lines · 43 tokens per session scan A 07d04d26d1b8

Subscribe to this mod's changes

checking-compliance is a skill published in the GitHub repository qte77/claude-code-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 768 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.

Claude CodeHardware and IoTLegal and complianceagent-skillsai-coding-toolsclaude-code-marketplaceclaude-code-pluginsclaude-code-skills
Related

Other skills, from other repositories

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

phuryn/pm-skills · 42 tokens

draft-nda

Draft a detailed Non-Disclosure Agreement between two parties covering information types, jurisdiction, and clauses needing legal review. Use when creating confidentiality agreements or preparing an NDA for a partnership.

phuryn/pm-skills · 39 tokens

pestle-analysis

Perform a PESTLE analysis covering Political, Economic, Social, Technological, Legal, and Environmental factors. Use when assessing the macro environment, doing strategic planning, or evaluating external factors affecting your business.

phuryn/pm-skills · 46 tokens

go-bulma

Scaffold the Bulma CSS framework into a Go web app with embedded assets for zero-dependency binaries. Use when building an HTML UI with a classes-based CSS framework and no Node toolchain.

sgaunet/claude-plugins · 44 tokens

privacy-policy

Drafts a jurisdiction-aware privacy policy for any digital product. Use whenever a PMM or Product Manager needs to create, update, audit or review data protection documentation, asks about GDPR, CCPA or UK GDPR obligations, mentions "privacy policy", "cookie policy", "data retention", "right to be forgotten", "data…

stefanoskarakasis/Product-Marketing-Skills · 84 tokens

esp32-expert

This skill should be used when the user is writing, reviewing, debugging, or architecting C++ firmware for ESP32 and variants (ESP32-S2, S3, C3, C6, H2, P4) using ESP-IDF or PlatformIO. Provides expert critique covering FreeRTOS task design, memory management (IRAM/DRAM/PSRAM), peripheral drivers (I2C/SPI/UART/GPIO)…

mathisk2095/jko-claude-plugins · 193 tokens