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 event4u-app/agent-config --skill license-compliance-creditsgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/license-compliance-credits)<a href="https://agentmods.dev/skills/event4u-app/agent-config/license-compliance-credits"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/license-compliance-credits/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/event4u-app/agent-config/license-compliance-credits"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/license-compliance-credits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 20 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 42 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 49 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00043 | $0.01115 |
| Opus 5 | $0.00022 | $0.00558 |
| Sonnet 5 | $0.00009 | $0.00223 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
license-compliance-credits 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 8d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
license-compliance-credits
When to use
provenance/borrows.jsonljust gained, lost, or changed a line (a new borrow was ledgered vialicense-compliance-borrow-check, or a correction line was appended).npx tsx node_modules/@event4u/agent-config/src/scripts/lint_provenance.tsreports the notices file is out of sync with the ledger.- Someone asks "are our third-party notices up to date?" or "regenerate the credits file".
Do NOT use when:
- You want to add a NEW borrow — that starts at
license-compliance-borrow-check; this skill only regenerates the derived file from an already-updated ledger. - The ledger itself needs fixing (a deny-class entry, a missing note) — fix
the offending line via
license-compliance-borrow-check's discipline first; this skill cannot repair a bad ledger, only render it.
Procedure
- Inspect the current state — read
provenance/borrows.jsonl(it may be legitimately empty) and note how many lines it has before regenerating, so the diff is checkable. - Regenerate the notices file:
npx tsx node_modules/@event4u/agent-config/src/scripts/lint_provenance.ts --regenerate-notices - Diff
docs/THIRD-PARTY-NOTICES.mdbefore vs. after — confirm only that generated file changed, and thatprovenance/borrows.jsonlitself was not touched (it is append-only; this command never writes to it). - Verify sync + validity with a plain run (no flag):
Exit code 0 confirms every ledger record is schema-valid, no deny-class ornpx tsx node_modules/@event4u/agent-config/src/scripts/lint_provenance.tsunknownlicense slipped through, no transformation note reads as rename-only, and the notices file now matches the ledger byte-for-byte. - If the linter fails, stop — do not hand-patch
docs/THIRD-PARTY-NOTICES.mdto make it pass. Fix the actual offending line inprovenance/borrows.jsonlvialicense-compliance-borrow-check, then re-run step 2.
What ships with it
1 file 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.
- 8d ago First seen · 98 lines · 43 tokens per session scan A 8fed82ed5166
license-compliance-credits is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,115 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-09-04.
Other skills, from other repositories
telnyx-email-suppressions-curl
Manage email suppressions (blocks), import and export suppression lists, and manage unsubscribe groups. Use for deliverability compliance and bounce handling.
healthcare-providers-verify
Validates practitioner credentials and license status against the NPI registry. Cross-references specialties, credentials, and practice addresses against official records. Returns Verified / Partially Verified / Unverified / Flagged per practitioner with mismatch details and source URLs. Triggers: "verify these…
python-packaging-license-finder
Use this skill to deterministically find license information for Python packages by checking PyPI metadata first, then falling back to Git repository LICENSE files using shallow cloning.
patent-review
Multi-round cyclic rigorous review of Chinese patent technical disclosure documents. Supports multi-dimension review (data flow closure, terminology consistency, state transition, formula completeness, error code routing, text-diagram consistency), round-by-round convergence, and optional auto-fix (default off, severe…
template-redacted-report
Redacted release-report exemplar for classification ceilings, source protection, source-safe ledgers, reviewer gates, and mosaic-risk checks.
disclosure-page-generator
When the user wants to create, optimize, or audit an affiliate, sponsor, or paid partnership disclosure page. Also use when the user mentions "disclosure," "affiliate disclosure," "sponsored content," "FTC disclosure," or "paid partnership." For sitewide page planning, use website-structure.