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 agentmods add skills/cvander/maya/compliance_checknpx skills add cvander/Maya --skill compliance_checkgit clone --depth 1 https://github.com/cvander/MayaWrote 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/cvander/maya/compliance_check)<a href="https://agentmods.dev/skills/cvander/maya/compliance_check"><img src="https://agentmods.dev/badge/skills/cvander/maya/compliance_check.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.00609 |
| Opus 5 | $0.00010 | $0.00304 |
| Sonnet 5 | $0.00004 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
compliance-check 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 4d 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.
What it actually says
Compliance Check
Reads staff-certs.md, cooler-temps.md, pest-log.md, and permits/README.md. Checks for expiring certifications, overdue logs, and upcoming permit renewals. Reports findings by severity.
Read-only. Does not modify files or reach external services.
When to Use
- Weekly compliance review (scheduled: Monday 9:00 AM)
- Before any scheduled inspection (ABC, SFDPH, SFFD)
- When onboarding new staff (check cert status)
- After receiving renewal notices from authorities
Procedure
Run the skill from the repo root:
# Human-readable summary
python -m skills.compliance_check
# Structured JSON output (for automation)
python -m skills.compliance_check --format json
# Check with a specific reference date
python -m skills.compliance_check --date 2025-06-01 --format json
# Custom look-ahead window
python -m skills.compliance_check --days-ahead 60 --format json
# Against a custom compliance directory
python -m skills.compliance_check --compliance-dir path/to/compliance --format json
Parse the JSON result:
status: "ok" (no issues) or "warn" (findings present)findings: array with codes CERT_EXPIRING, CERT_EXPIRED, LOG_OVERDUE, PERMIT_RENEWAL, INSPECTION_DUEdata.certs_checked: number of staff certs scanneddata.logs_checked: number of compliance logs scanneddata.permits_checked: number of permits scanned
Exit Codes
| Code | Meaning |
|---|---|
| 0 | All compliance items current |
| 1 | One or more compliance findings |
| 2 | Config error (bad arguments) |
| 3 | Data error (can't read compliance files) |
| 10 | Unexpected error |
Verification
After running, confirm:
- Exit code is 0 or 1 (not 2, 3, or 10)
- stdout is valid JSON (when using --format json)
data.certs_checked>= 0 (files were actually read)- If exit code is 1,
findingsarray is non-empty
What ships with it
16 files 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.
- __init__.py 106 B runs code
- __main__.py 694 B runs code
- fixtures/FIXTURES.md 207 B
- fixtures/happy_path/compliance/cooler-temps.md 562 B
- fixtures/happy_path/compliance/pest-log.md 488 B
- fixtures/happy_path/compliance/staff-certs.md 524 B
- fixtures/happy_path/expected.json 290 B
- fixtures/happy_path/permits/README.md 701 B
- fixtures/warn_case/compliance/cooler-temps.md 378 B
- fixtures/warn_case/compliance/pest-log.md 404 B
- fixtures/warn_case/compliance/staff-certs.md 553 B
- fixtures/warn_case/expected.json 1.2 KB
- fixtures/warn_case/permits/README.md 701 B
- main.py 11 KB runs code
- manifest.toml 340 B
- test_main.py 6.0 KB runs code
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.
- 4d ago First seen · 80 lines · 21 tokens per session scan A b79cc5edf86c
compliance-check is a skill published in the GitHub repository cvander/Maya (10 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 609 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
tooluniverse-drug-research
Comprehensive drug profiling — mechanism, primary/secondary targets, drug interactions, clinical-trial status, adverse events (FAERS), pharmacogenomics, and approval history. Use for full drug investigation reports, 'tell me about drug X' queries, and assembling drug profiles for clinicians, researchers, or regulatory…
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
catalyst-center-readonly
Query Cisco Catalyst Center read-only — device inventory, site hierarchy, wireless, assurance health, compliance, software images, events. All 514 read-only API operations reachable through 8 grouped dispatchers. Use when asked what Catalyst Center manages, where a device sits, what its health or compliance state is…
build-audit-logs
Build or review audit trails in TypeScript/JavaScript apps using evlog (pipelines, typed actions, denials, retention, compliance-style reviews). For application code, not for extending the evlog package.
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…