compliance-docs

compliance-docs is a skill for Claude Code, Codex from cvander/Maya. It costs 13 tokens per session (508 once invoked), scanned A, original, MIT.

A read-only audit of compliance documentation, such as required markdown files and permits or README files. It reports documents that are missing, empty, or more than 30 days old.

In plain words
What is it for?
Use it for monthly documentation checks, inspection preparation, onboarding a manager, or reviewing records after opening a new bar location.
Why use it?
It shows whether the expected records are present and current before an inspection, scheduled review, or management handover. It does not edit files or contact outside services.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for monthly documentation checks, inspection preparation, onboarding a manager, or reviewing records after opening a new bar location.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cvander/maya/compliance_docs
View source ↗ cvander/Maya
Install

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.

Any agent
npx skills add cvander/Maya --skill compliance_docs
Clone the repo
git clone --depth 1 https://github.com/cvander/Maya

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for compliance-docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/cvander/maya/compliance_docs/github.svg)](https://agentmods.dev/skills/cvander/maya/compliance_docs)
Your own site
<a href="https://agentmods.dev/skills/cvander/maya/compliance_docs"><img src="https://agentmods.dev/badge/skills/cvander/maya/compliance_docs/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.

agentmods 80×15 button for compliance-docs

Your own site · 80×15
<a href="https://agentmods.dev/skills/cvander/maya/compliance_docs"><img src="https://agentmods.dev/badge/skills/cvander/maya/compliance_docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 508 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.00508
Opus 5.5 $0.00005 $0.00203
Sonnet 5.5 $0.00003 $0.00102
Haiku 4.5 $0.00001 $0.00051

Measured 2mo ago against content hash 42b24e291296, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

compliance-docs 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.

The scan reads SKILL.md. This mod also ships 4 executable files (__init__.py, __main__.py, main.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/compliance_docs/SKILL.md · 71 lines

What it actually says

Compliance Docs

Reads all compliance markdown files and permits/README.md. Reports which expected docs exist, which are missing, which are empty, and which are stale (not updated in >30 days).

Read-only. Does not modify files or reach external services. No PII in output.

When to Use

  • Monthly documentation audit (scheduled: 1st of month)
  • Before any scheduled inspection (to verify docs are in order)
  • When onboarding a new manager (verify all docs exist)
  • After setting up a new bar location

Procedure

Run the skill from the repo root:

# Human-readable summary
python -m skills.compliance_docs

# Structured JSON output (for automation)
python -m skills.compliance_docs --format json

# Against a custom compliance directory
python -m skills.compliance_docs --compliance-dir path/to/compliance --format json

Parse the JSON result:

  • status: "ok" (all docs present and current) or "warn" (findings present)
  • findings: array with codes DOC_MISSING, DOC_EMPTY, DOC_STALE
  • data.docs_checked: number of docs audited
  • data.docs_present: number of docs found
  • data.docs_missing: number of expected docs not found

Exit Codes

Code Meaning
0 All expected docs present and current
1 One or more documentation issues
2 Config error (bad arguments)
3 Data error (can't read directory)
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.docs_checked > 0 (directory was actually read)
  • If exit code is 1, findings array is non-empty
Changes

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.

  1. 2mo ago First seen · 71 lines · 13 tokens per session scan A 42b24e291296

Subscribe to this mod's changes

compliance-docs is a skill published in the GitHub repository cvander/Maya (11 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 508 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-31.

Related

compliance-docs compared with skills from other repositories

compliance-docs next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
compliance-docscvander/MayaSkill115mo agoMITA13Claude Code, Codex
fto-triageanthropics/claude-for-legalSkill9.9k3d agoApache-2.0A81Claude Code
legal-holdanthropics/claude-for-legalSkill9.9k3d agoApache-2.0A68Claude Code
specification-writingwanshuiyin/Auto-claude-code-research-in-sleepSkill19k3d agoMITA49Claude Code
terms-of-servicegenspark-ai/genofficeSkill12kyesterdayApache-2.0A32Claude Code, Codex
x-scorecardx-cmd/x-cmdSkill4.7k7d agoApache-2.0A57Claude Code, Codex
gesellschaftsrechtliche-satzungen-agbKlotzkette/claude-fuer-deutsches-rechtSkill1.8kyesterdayApache-2.0A69Claude Code