What is compliance-docs?

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.

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

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.

compliance-docs — Skill by cvander

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.

agentmods

npx agentmods add skills/cvander/maya/compliance_docs

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.

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. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00013	$0.00508
Opus 5	$0.00006	$0.00254
Sonnet 5	$0.00003	$0.00102
Haiku 4.5	$0.00001	$0.00051

Measured 2d ago against content hash 42b24e291296, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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

Files

What ships with it

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

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.

2d 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 (10 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 508 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.

Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens