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 agentmods add skills/qte77/claude-code-plugins/checking-compliancenpx skills add qte77/claude-code-plugins --skill checking-compliancegit clone --depth 1 https://github.com/qte77/claude-code-pluginsWhat 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 | $0.00043 | $0.00768 |
| Opus 5 | $0.00022 | $0.00384 |
| Sonnet 5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
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 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.
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 scopereferences/requirement-hierarchy.md— SYS-REQ → PRD-REQ → SW-REQ ID conventions
Workflow
- Parse device description — Identify device type, markets (EU/US/both), wireless capability, power source, intended use
- 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)
- WebSearch for latest standard revisions if unsure about current edition
- Generate compliance checklist at
docs/compliance-checklist.mdwith:- Each applicable directive/standard
- Specific clauses relevant to the device type
- Test requirements (pre-compliance and certification)
- Generate requirements file at
docs/requirements.mdwith 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)
- 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 |
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.
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 · 77 lines · 43 tokens per session scan A 07d04d26d1b8
checking-compliance is a skill published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 43 tokens to every session and 768 once invoked, about $0.0002 per session on Opus 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
orchestrator
FULLY AUTONOMOUS Flutter development pipeline orchestrator. Smart routing: PM analyzes -> creates targeted tasks -> Orchestrator executes only needed agents. Supports Asana task URLs. Includes QE verification via Maestro E2E tests. 7-phase flow: PM -> TodoWrite -> Execute -> Review -> Tests -> QE E2E -> Close.
flutter-guide
Flutter/BLoC Clean Architecture patterns, review checklists, and testing guides. Background knowledge for flutter-dev, flutter-reviewer, flutter-tester. Not user-invocable.
maestro-flutter
Maestro E2E testing knowledge for Flutter apps. YAML-based flows, TestKeys, visual regression, Maestro MCP integration. Background knowledge for QE E2E testing phase.
android-kotlin-compose
Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…
android-kotlin-coroutines
Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…
codex-advisor
Advisory consultation skill for architectural reviews, design decisions, code analysis, and technology evaluation. Codex provides recommendations without making code changes. Invoked by phrases like "consult Codex", "get Codex's opinion", "ask Codex about", "have Codex review", "Codex analysis", "validate this…