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 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/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/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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00034 | $0.02708 |
| Opus 5.5 | $0.00014 | $0.01083 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (35 stars, last pushed 15d ago), licensed MIT. It adds 34 tokens to every session and 2,708 once invoked, about $0.0001 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-30.
Other skills, from other repositories
gwm
Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…
open-sourcing
This skill should be used when the user asks to "open source this project", "prepare this repository for public release", "make this repo public", "check open-source readiness", "choose a license for this project", or "set up release automation" ahead of a public launch. Provides a release-readiness workflow covering…
repo-prep
Interactively prepare a code repository for publication — LICENSE, NOTICE, AUTHORSHIP, README sections, package metadata, .gitignore, community docs (CONTRIBUTING/CODEOFCONDUCT/SECURITY/CHANGELOG), .github templates (issues/PR/CI/dependabot), a promo "more from the author" block, and conditional EU/Germany legal…
open-source
Open source readiness best practices. Covers licensing, documentation, community health, CI/CD, compliance, legal, and packaging. USE WHEN: user mentions "open source", "license", "LICENSE", "CONTRIBUTING", "CODEOFCONDUCT", "CHANGELOG", "open source readiness", "community health", "OSS compliance", "SPDX", "CLA"…
community-health
Guide for setting up GitHub community health files for open source repositories. Use when preparing repos for public release, adding community standards files, or configuring issue/PR templates.
release-guard
Block releases that fail the licence and changelog policy, and bundle the team's release tooling into one installable package.