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/shashionline/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/shashionline/indian-law-plugin/pil-viability)<a href="https://agentmods.dev/commands/shashionline/indian-law-plugin/pil-viability"><img src="https://agentmods.dev/badge/commands/shashionline/indian-law-plugin/pil-viability/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/shashionline/indian-law-plugin/pil-viability"><img src="https://agentmods.dev/badge/commands/shashionline/indian-law-plugin/pil-viability.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.00051 | $0.04129 |
| Opus 5 | $0.00026 | $0.02065 |
| Sonnet 5 | $0.00010 | $0.00826 |
| Haiku 4.5 | $0.00005 | $0.00413 |
Grade A, and why
pil-viability 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 10d 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.
This is a copy
100% identical to pil-viability — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pil-viability - Public Interest Litigation Assessment
Command Purpose
Assess viability of filing Public Interest Litigation (PIL) for social justice causes, environmental protection, corruption exposure, or enforcement of diffused/collective rights. Evaluates bonafide intent, public interest element, evidence strength, and strategic litigation approach.
How It Works
This command invokes the pil-environmental-specialist agent to:
- Distinguish PIL from private writ (public vs. individual interest)
- Assess petitioner's bonafide intent and credibility
- Evaluate public interest magnitude
- Recommend PIL vs. alternative remedies (SPCB, NGT, RTI, etc.)
- Provide evidence gathering strategy
- Assess likelihood of admission and success
When to Use
- Environmental violations (pollution, illegal construction in forests, mining)
- Rights of marginalized groups (slum dwellers, bonded laborers, prisoners, tribals)
- Corruption in public projects (tender irregularities, misuse of public funds)
- Systemic violations (government school infrastructure, public health, sanitation)
- Government inaction affecting large population
- Transparency issues (denial of public information systemically)
When NOT to Use (Private Writ, Not PIL)
- Your own passport delay (personal issue)
- Your property dispute (private matter)
- Your employment termination (service matter - CAT)
- Single individual affected (not public/large group)
Usage
/pil-viability
OR with cause context:
/pil-viability Industrial pollution affecting entire village
/pil-viability Government schools lack toilets for girl students across district
Workflow
When you invoke /pil-viability, I will:
Step 1: Issue Classification - PIL or Private Remedy?
I'll ask you targeted questions:
Q1: What is the issue?
- Describe the problem/violation
Q2: Who is affected?
- Just you (individual)?
- Large section of public / Community / Marginalized group?
- How many people affected? (Approx.)
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.
- 10d ago First seen · 492 lines · 51 tokens per session scan A 2406be3ff702
pil-viability is a command published in the GitHub repository shashionline/indian-law-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 4,129 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to pil-viability, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
review-policy
Review a policy document for structure, coverage, and language quality.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.