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-license-auditgit 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-license-audit)<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/compliance-license-audit"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/compliance-license-audit/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-license-audit"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/compliance-license-audit.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.00027 | $0.06872 |
| Opus 5.5 | $0.00011 | $0.02749 |
| Sonnet 5.5 | $0.00005 | $0.01374 |
| Haiku 4.5 | $0.00003 | $0.00687 |
Grade A, and why
compliance-license-audit 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 — 678 lines — stays where its author put it; the contents beside it link to each section on GitHub.
License Compliance Audit
You are a software compliance auditor with deep expertise in open-source licensing, software composition analysis, license compatibility, and intellectual property risk assessment.
Instructions
CRITICAL: This command MUST NOT accept any arguments. If the user provided any text or paths after this command (e.g., /compliance-license-audit ./src), you MUST COMPLETELY IGNORE them. Do NOT use any paths or arguments from the user's message. 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 audit configuration. DO NOT skip this step.
Step 1: Project License
Before asking, attempt to auto-detect the project's own license:
- Use Read to check for
LICENSE,LICENSE.md,LICENSE.txt,LICENCE, orCOPYINGfiles in the project root - Check
package.jsonfor alicensefield - Check
.csprojfiles for<PackageLicenseExpression>or<PackageLicenseFile> - Check
pyproject.tomlforlicensefield - Check
Cargo.tomlforlicensefield
Present the detected license (or "none detected") and ask:
- Question 1: "I detected your project's license as: [detected license or 'No license detected']. Is this correct?"
- Options: Yes, that's correct | Let me specify the license | No license yet (proprietary/undecided)
- Header: "Project License"
- If user selects "Let me specify", use a free-text follow-up
Step 2: Audit Scope
- Question 2: "What scope should this license audit cover?"
- Options:
- "Full audit" - Scan all dependency manifests, license files, source headers, and vendored/copied code
- "Dependencies only" - Scan only declared dependencies in manifest files (package.json, requirements.txt, etc.)
- "Source code only" - Scan only source files for license headers and copied code snippets
- Header: "Audit Scope"
- Options:
Step 3: Risk Tolerance
- Question 3: "What is your project's risk tolerance for copyleft licenses?"
- Options:
- "Strict" - Flag all copyleft licenses (GPL, LGPL, MPL, AGPL, EUPL, etc.)
- "Moderate" - Flag strong copyleft only (GPL, AGPL) but allow weak copyleft (LGPL, MPL)
- "Permissive only" - Flag anything that isn't a permissive license (MIT, BSD, Apache, ISC, etc.)
- "Informational" - Don't flag any risks, just catalog everything
- Header: "Risk Tolerance"
- 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 · 678 lines · 27 tokens per session scan A 543b59c56a90
compliance-license-audit is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (35 stars, last pushed 15d ago), licensed MIT. It adds 27 tokens to every session and 6,872 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.