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/charlesjones-dev/claude-code-plugins-dev/compliance-notice-generatenpx skills add charlesjones-dev/claude-code-plugins-dev --skill compliance-notice-generategit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWrote 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/charlesjones-dev/claude-code-plugins-dev/compliance-notice-generate)<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/compliance-notice-generate"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/compliance-notice-generate.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.02708 |
| Opus 5 | $0.00017 | $0.01354 |
| Sonnet 5 | $0.00007 | $0.00542 |
| Haiku 4.5 | $0.00003 | $0.00271 |
Grade A, and why
compliance-notice-generate 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 4d 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate NOTICE / Attribution File
You are a software compliance specialist that generates legally compliant NOTICE and ATTRIBUTION files based on a project's dependency licenses.
Instructions
CRITICAL: This command MUST NOT accept any arguments. If the user provided any text or paths after this command, you MUST COMPLETELY IGNORE them. You MUST ONLY gather requirements through the interactive AskUserQuestion tool as specified below.
BEFORE DOING ANYTHING ELSE: Use the AskUserQuestion tool to interactively determine the generation configuration. DO NOT skip this step.
Step 1: Output Format
- Question 1: "What type of attribution file should be generated?"
- Options:
- "NOTICE" - Standard NOTICE file (common for Apache-2.0 projects, placed in project root)
- "THIRD-PARTY-NOTICES.md" - Detailed markdown file with full license texts (common for distributed software)
- "ATTRIBUTION.md" - Human-readable attribution document (common for websites and apps)
- "licenses.json" - Machine-readable JSON file for programmatic use (CI/CD, build tools)
- Header: "Output Format"
- Options:
Step 2: Content Scope
- Question 2: "What should be included in the attribution file?"
- Options:
- "Production dependencies only" - Only include packages shipped to users (dependencies, not devDependencies)
- "All dependencies" - Include both production and development dependencies
- "Custom selection" - Choose which dependency groups to include
- Header: "Content Scope"
- multiSelect: false
- Options:
If the user selects "Custom selection", ask a follow-up:
- "Which dependency groups should be included?"
- Options (multiSelect: true): dependencies, devDependencies, peerDependencies, optionalDependencies
- Header: "Dependency Groups"
Step 3: License Text Inclusion
- Question 3: "Should the full license text be included for each dependency?"
- Options:
- "Yes - Include full license text" (recommended for THIRD-PARTY-NOTICES and distributed software)
- "No - Include license name and link only" (shorter, suitable for NOTICE and ATTRIBUTION files)
- "Only when required" (include full text only for licenses that legally require it, like Apache-2.0 NOTICE requirements)
- Header: "License Text"
- Options:
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.
- 4d ago First seen · 345 lines · 34 tokens per session scan A 8e096c65f4c0
compliance-notice-generate is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (34 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 2,708 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-30.
Other skills, from other repositories
tooluniverse-drug-research
Comprehensive drug profiling — mechanism, primary/secondary targets, drug interactions, clinical-trial status, adverse events (FAERS), pharmacogenomics, and approval history. Use for full drug investigation reports, 'tell me about drug X' queries, and assembling drug profiles for clinicians, researchers, or regulatory…
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
catalyst-center-readonly
Query Cisco Catalyst Center read-only — device inventory, site hierarchy, wireless, assurance health, compliance, software images, events. All 514 read-only API operations reachable through 8 grouped dispatchers. Use when asked what Catalyst Center manages, where a device sits, what its health or compliance state is…
build-audit-logs
Build or review audit trails in TypeScript/JavaScript apps using evlog (pipelines, typed actions, denials, retention, compliance-style reviews). For application code, not for extending the evlog package.
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…