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/vaquarkhan/compliance-agent-skillsWrote 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/rules/vaquarkhan/compliance-agent-skills/10-deterministic-audit)<a href="https://agentmods.dev/rules/vaquarkhan/compliance-agent-skills/10-deterministic-audit"><img src="https://agentmods.dev/badge/rules/vaquarkhan/compliance-agent-skills/10-deterministic-audit/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/rules/vaquarkhan/compliance-agent-skills/10-deterministic-audit"><img src="https://agentmods.dev/badge/rules/vaquarkhan/compliance-agent-skills/10-deterministic-audit.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.00305 | $0.00305 |
| Opus 5 | $0.00152 | $0.00152 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
10-deterministic-audit 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 9d 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
Deterministic Audit
Rules
- Never invent CFR sections, PCI requirement numbers, or TSC control IDs.
- Cite sources when stating requirements (e.g., "PCI-DSS v4.0 Req 6.4.3", "45 CFR §164.312(b)", "SOC 2 CC7.2").
- Load the matching skill before deep audit work — see
30-framework-routing.mdc. - Emit artifacts with engagement ID, UTC timestamps, and SHA-256 hashes for evidence files.
- Record gaps as findings with severity, control ID, observation, recommendation, owner, due date.
Finding format
id: FIND-001
severity: HIGH # CRITICAL | HIGH | MEDIUM | LOW | INFO
control_id: PCI-6.4.3
observation: "Third-party script lacks authorization record"
recommendation: "Document business justification and link change ticket"
owner: ""
due_date: null
status: open
Anti-patterns
- "You are fully compliant" without evidence
- Generic security advice unrelated to scoped frameworks
- Skipping
/scopeon multi-system engagements
Templates
Use scaffolds in templates/ — do not freehand evidence manifests.
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.
- 9d ago First seen · 39 lines · 305 tokens per session scan A 181a0f33748a
10-deterministic-audit is a cursor rule published in the GitHub repository vaquarkhan/compliance-agent-skills (2 stars, last pushed 15d ago), licensed MIT. It adds 305 tokens to every session, about $0.0015 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 cursor rules, from other repositories
compliance-trestle
Compliance Trestle repository rules.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.