Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/MauricioPerera/KDDnpx agentmods add skills/mauricioperera/kdd/kdd-compliance-scanWrote 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/mauricioperera/kdd/kdd-compliance-scan)<a href="https://agentmods.dev/skills/mauricioperera/kdd/kdd-compliance-scan"><img src="https://agentmods.dev/badge/skills/mauricioperera/kdd/kdd-compliance-scan/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/mauricioperera/kdd/kdd-compliance-scan"><img src="https://agentmods.dev/badge/skills/mauricioperera/kdd/kdd-compliance-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 50 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.00125 | $0.01742 |
| Opus 5.5 | $0.00050 | $0.00697 |
| Sonnet 5.5 | $0.00025 | $0.00348 |
| Haiku 4.5 | $0.00013 | $0.00174 |
Grade A, and why
kdd-compliance-scan 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 2mo 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance Scan (Capa 3 de KDD -- licencias)
Produce hallazgos de compatibilidad de licencias de dependencias en el formato de contrato que audita la Capa 3 de KDD. Esta skill NO es el gate -- es la parte creativa/no determinista (normalizar la salida de un scanner de licencias a un juicio de compatibilidad) que el gate despues valida. Distincion central: el agente/scanner decide la categoria y compatibilidad de cada licencia; el gate solo audita que el artefacto sellado cumpla forma y politica de calidad de datos.
A diferencia de kdd-security-scan, este dominio
NO vendoriza ningun sellador externo: la identidad de un finding (nombre+version de
dependencia) ya la resuelve de forma estable la herramienta de licencias del
ecosistema del repo, asi que no hace falta un finalizer aparte -- vos mismo escribis
findings.json ya en forma final.
Cuando usarla
El usuario pide auditar las licencias de las dependencias de un repo (propio o externo) y quiere el resultado gobernado por KDD (versionable, gateado en CI, con politica declarativa), no un reporte suelto en prosa.
Insumos que necesitas antes de empezar
repo_root: raiz del repositorio a escanear.project_license: identificador SPDX de la licencia del propio proyecto (leelo deLICENSE/package.json/Cargo.toml/etc. -- si no esta declarada, decilo explicito en el reporte en vez de adivinar).scan_dir: donde vas a escribirfindings.json. Por defectocompliance/scandentro del repo KDD (coincide con el default devalidate_compliance_findings.py); si estas gobernando un repo EXTERNO, cualquier directorio disponible sirve, con tal de pasarselo explicito al gate.- El schema completo vive en
knowledge/data_models/compliance/findings.schema.json-- consultalo si dudas de un campo, no adivines la forma.
Flujo
1. Elegi el scanner del ecosistema
No reimplementes deteccion de licencias: corre la herramienta estandar del ecosistema del repo y consumi su salida JSON.
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.
- 2mo ago First seen · 144 lines · 125 tokens per session scan A f64ac98d8285
kdd-compliance-scan is a skill published in the GitHub repository MauricioPerera/KDD (11 stars, last pushed yesterday), licensed MIT. It adds 125 tokens to every session and 1,742 once invoked, about $0.0005 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-31.
Other skills, from other repositories
crit-cli
Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR or GitLab MR, or read/interpret a crit review JSON file.…
crit
Review code changes, a plan, a live page (running dev server), or a local HTML file with Crit inline comments and structured human feedback. Use only when the user explicitly invokes /crit or directly asks to use Crit; a generic review request does not count.
crit-story
Author a crit story and continue the interactive review loop only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
policy-drift-audit
Run the policy/process drift audit. Surfaces stale, superseded, duplicate, non-canonical, and conflicting policy documents using DocGraph's built-in drift engine. Presents findings and optional remediation suggestions without writing governance decisions.
access-review
Conduct periodic access reviews and certifications. Implement access governance and recertification workflows. Use when managing access compliance.
pseudonymizing-for-gdpr
Apply GDPR-grade pseudonymization to clinical or personal text with OpenMed, keeping a separately-held re-linkage key so the data can be controlled-re-linked later. Use when the user must process EU personal/health data under GDPR, asks for pseudonymization vs anonymization, needs Art. 4(5) / Art. 9 / Recital 26…