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/kousthubha-sky/indian-law-pluginWrote 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/kousthubha-sky/indian-law-plugin/cursor-rules)<a href="https://agentmods.dev/rules/kousthubha-sky/indian-law-plugin/cursor-rules"><img src="https://agentmods.dev/badge/rules/kousthubha-sky/indian-law-plugin/cursor-rules/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/kousthubha-sky/indian-law-plugin/cursor-rules"><img src="https://agentmods.dev/badge/rules/kousthubha-sky/indian-law-plugin/cursor-rules.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.00018 | $0.00264 |
| Opus 5.5 | $0.00007 | $0.00106 |
| Sonnet 5.5 | $0.00004 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
cursor-rules 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.
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
Indian Law Compliance Audit
This project includes the indian-law-compliance skill (https://github.com/kousthubha-sky/indian-law-plugin).
When asked to audit compliance, or before building features that touch personal data, payments, auth, or user-generated content:
- Read
skills/india-compliance-audit/SKILL.mdand follow its workflow exactly. - Rule packs (DPDP, IT Act, CERT-In, RBI, accessibility, etc.) are in
skills/india-compliance-audit/rules/. - Run
node detectors/run-detectors.mjs <path>for deterministic findings (Aadhaar/PAN/IFSC in code, missing policy files, weak hashing, accessibility gaps). - Write results to
india-compliance-report.mdin the project root, followingskills/india-compliance-audit/references/report-format.md.
This is NOT legal advice. It flags technical signals and cites law. Consult a qualified legal professional for compliance decisions.
Requires the skills/ and detectors/ folders from this plugin copied into your project.
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.
- 2mo ago First seen · 26 lines · 18 tokens per session scan A 478ed8101174
cursor-rules is a cursor rule published in the GitHub repository kousthubha-sky/indian-law-plugin (1 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 264 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.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).