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/Project-VIC-International/Agentic-AI-Development-CourseWrote 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/project-vic-international/agentic-ai-development-course/security-compliance)<a href="https://agentmods.dev/rules/project-vic-international/agentic-ai-development-course/security-compliance"><img src="https://agentmods.dev/badge/rules/project-vic-international/agentic-ai-development-course/security-compliance/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/project-vic-international/agentic-ai-development-course/security-compliance"><img src="https://agentmods.dev/badge/rules/project-vic-international/agentic-ai-development-course/security-compliance.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.04002 | $0.04002 |
| Opus 5.5 | $0.01601 | $0.01601 |
| Sonnet 5.5 | $0.00800 | $0.00800 |
| Haiku 4.5 | $0.00400 | $0.00400 |
Grade A, and why
security-compliance 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 18d 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.
How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Compliance: Choose Your Framework, Then Implement the Controls
This project processes law-enforcement-sensitive information and evidence — potentially including CSAM in crimes-against-children casework. All code MUST meet the security control framework that applies to the agency that will operate the tool. Non-compliance is not a bug — it is a deployment blocker, and in many jurisdictions a legal liability for the agency operating the tool.
This rule uses NIST SP 800-53 Rev. 5 control families as a common, widely mapped baseline. Most national frameworks map to it, but they are not the same, so you must also apply your own jurisdiction's framework.
The constitution's "Security and Privacy" section is the high-level statement. This rule is the enforceable detail the agent applies when writing code.
The full mappings should live in your repo at docs/security/nist-800-53-mapping.md and a mapping for your jurisdiction's framework (for example docs/security/cjis-compliance-mapping.md, docs/security/ism-mapping.md, or docs/security/nzism-mapping.md). Update them every time a new feature touches a control family.
Choose the Control Framework First
Before writing security-relevant code, the agent MUST ask the user which country and type of agency will operate the tool, record the answer in the constitution or project context, and plan for that framework. Do not assume the United States. Examples:
| Where the tool will run | Typical frameworks to confirm with the agency |
|---|---|
| United States, criminal justice information (CJI) | FBI CJIS Security Policy (use the current version) plus NIST SP 800-53 Rev. 5 |
| Australia | Australian Government Information Security Manual (ISM), Protective Security Policy Framework (PSPF), Essential Eight, Privacy Act 1988, plus state or territory rules |
| New Zealand | NZ Information Security Manual (NZISM), Protective Security Requirements (PSR), Privacy Act 2020 |
| European Union / United Kingdom | GDPR and the Law Enforcement Directive (EU) 2016/680; UK GDPR and Data Protection Act 2018 Part 3 |
| Other countries, or not yet known | National law-enforcement and privacy rules, with NIST SP 800-53 Rev. 5 and ISO/IEC 27001 as a neutral baseline |
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.
- 18d ago Changed · +18 lines · +464 tokens per session 39cf59880e1b
- 2mo ago First seen · 182 lines · 3,538 tokens per session scan A 9e1e0e31c66f
security-compliance is a cursor rule published in the GitHub repository Project-VIC-International/Agentic-AI-Development-Course (5 stars, last pushed 14d ago), licensed Apache-2.0. It adds 4,002 tokens to every session, about $0.0160 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.
Other cursor rules, from other repositories
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.