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.
git clone --depth 1 https://github.com/gonzalezpazmonica/saviaWrote 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/commands/gonzalezpazmonica/savia/compliance-matrix)<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/compliance-matrix"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/compliance-matrix/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/commands/gonzalezpazmonica/savia/compliance-matrix"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/compliance-matrix.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00051 | $0.00801 |
| Opus 5 | $0.00026 | $0.00400 |
| Sonnet 5 | $0.00010 | $0.00160 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
compliance-matrix 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- compliance-matrix — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Descripción
Comando para gestionar matrices de conformidad regulatoria del hardware. Almacena datos en projects/{proyecto}/hardware/compliance/ y registra requerimientos, estado de cumplimiento y evidencia de certificación.
Subcomandos
standard
Define un estándar de conformidad regulatoria.
compliance-matrix standard <proyecto> --name=CE --description="Marcado CE Directiva 2014/30/UE" \
--scope="EMC electromagnetic compatibility" --deadline=2026-06-30
Estándares soportados:
- CE (Comunidad Europea)
- FCC (USA)
- UL (Seguridad USA/Canadá)
- RoHS (Sustancias restringidas)
- ISO (normas internacionales)
status
Muestra estado de conformidad por requisito.
compliance-matrix status <proyecto> --standard=CE
compliance-matrix status <proyecto> --filter=pending
Estados: pass, fail, pending, NA (no aplica).
export
Genera reporte de matriz de conformidad.
compliance-matrix export <proyecto> --format=markdown
compliance-matrix export <proyecto> --format=docx --output=compliance.docx
gap
Identifica requisitos sin evidencia o incumplidos.
compliance-matrix gap <proyecto> --standard=FCC
Retorna lista de gaps con acción recomendada.
evidence
Vincula documento de evidencia a requisito de conformidad.
compliance-matrix evidence <proyecto> --req=CE-001 --file=test-report.pdf \
--description="Prueba EMC realizada por laboratorio certificado"
Estructura de almacenamiento
{
"proyecto": "smart-meter",
"standards": [
{
"id": "CE",
"name": "Marcado CE",
"requirements": [
{
"id": "CE-001",
"description": "Compatibilidad electromagnética",
"status": "pending",
"evidence_ref": null,
"responsible": "[email protected]",
"deadline": "2026-06-30"
}
]
}
]
}
Matriz de requisitos típicos
CE Mark
- EMC (Electromagnetic Compatibility)
- Seguridad eléctrica (Low Voltage Directive)
- Eficiencia energética
- Restricción de sustancias (RoHS)
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.
- 6d ago First seen · 129 lines · 51 tokens per session scan A 617c44211cf2
compliance-matrix is a command published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 801 once invoked, about $0.0003 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-06.
Other commands, from other repositories
arckit.eu-data-act
You are helping an enterprise architect generate a EU Data Act Compliance Assessment (Regulation EU 2023/2854) for an organisation that manufactures connected products, holds data generated by those products, or provides data processing services. Most Data Act obligations apply from 12 September 2025.
compliance-matrix
Gestiona matriz de conformidad con estándares regulatorios (CE, FCC, UL, RoHS, ISO). Permite definir estándares, trackear estado de requisitos, vincular evidencia, identificar gaps y generar reportes de cumplimiento.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.