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/commands/kousthubha-sky/indian-law-plugin/india-checklist)<a href="https://agentmods.dev/commands/kousthubha-sky/indian-law-plugin/india-checklist"><img src="https://agentmods.dev/badge/commands/kousthubha-sky/indian-law-plugin/india-checklist/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/commands/kousthubha-sky/indian-law-plugin/india-checklist"><img src="https://agentmods.dev/badge/commands/kousthubha-sky/indian-law-plugin/india-checklist.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.00022 | $0.01570 |
| Opus 5 | $0.00011 | $0.00785 |
| Sonnet 5 | $0.00004 | $0.00314 |
| Haiku 4.5 | $0.00002 | $0.00157 |
Grade A, and why
india-checklist 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 11d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/india-checklist
Interactive non-code compliance checklist for Indian law items that cannot be verified from the codebase — business registration, appointments, insurance, operational procedures.
Usage
/india-checklist
/india-checklist <area>
Area values: dpdp, cert-in, rbi, business, health, all
What this command does
Ask the user a series of yes/no/partial questions about non-code compliance items. For each item:
- State the obligation in plain language
- State the law and section
- Ask: "Done / In progress / Not done / Not applicable"
- If "Not done": give a concrete first action to take
At the end: print a summary of gaps with severity and first-action steps.
Checklist items (by area)
DPDP Act — non-code items
- Data Protection Officer (DPO) appointed? (Required if designated Significant Data Fiduciary — check meity.gov.in for SDF list)
- Annual Data Protection Impact Assessment (DPIA) conducted? (SDF requirement)
- Consent Manager integration live? (All Data Fiduciaries — deadline verify at meity.gov.in)
- Privacy policy reviewed by legal counsel for DPDP Rules 2025 compliance?
- Breach notification template prepared for DPBI? (meity.gov.in for current DPBI contact)
- User consent records archived for 7 years?
- Data retention schedule documented and enforced? (delete data when purpose ends)
- Sub-processor contracts (Data Processing Agreements) in place with all third-party vendors?
Consent flows — DPDP Act §6
- Separate opt-in consent collected for each distinct purpose? (not bundled "I agree to T&C and Privacy Policy")
- Consent collected BEFORE data collection starts — not post-signup retroactively?
- Consent withdrawal available and as easy as giving it? (e.g. "Manage preferences" / "Withdraw consent" in account settings)
- Consent records stored with: timestamp, purpose, version of privacy policy shown at time of consent?
- If children's data collected: verifiable parental consent mechanism in place?
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.
- 11d ago First seen · 115 lines · 22 tokens per session scan A a81b94245cd2
india-checklist is a command published in the GitHub repository kousthubha-sky/indian-law-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 1,570 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.
Other commands, from other repositories
ai-act-scan
Scan a codebase for EU AI Act compliance evidence and gaps. Produces a dimension-scored report with per-file findings, architecture graph, and prioritized recommendations.
ai-act-article
Show which analyzers, compliance dimensions, and current findings in this codebase map to a specific EU AI Act article.
service-auditor-prep
Generate complete auditor-ready evidence package for SOC 2.
soa-generator
Generate ISO 27001 Statement of Applicability (SOA) with control selection justifications.
overlay-apply
Apply NIST 800-53 overlays (FedRAMP, DoD, Privacy, etc.) to existing baselines.
ssp-section-generate
Generate System Security Plan (SSP) sections for NIST 800-53 controls.