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/check-jurisdiction)<a href="https://agentmods.dev/commands/shashionline/indian-law-plugin/check-jurisdiction"><img src="https://agentmods.dev/badge/commands/shashionline/indian-law-plugin/check-jurisdiction/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/check-jurisdiction"><img src="https://agentmods.dev/badge/commands/shashionline/indian-law-plugin/check-jurisdiction.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.00001 | $0.01493 |
| Opus 5 | $0.00000 | $0.00746 |
| Sonnet 5 | $0.00000 | $0.00299 |
| Haiku 4.5 | $0.00000 | $0.00149 |
Grade A, and why
check-jurisdiction 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 12d 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 check-jurisdiction — 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/check-jurisdiction - Jurisdiction Analysis Command
Description
Determine correct court jurisdiction (pecuniary, territorial, subject-matter) for filing civil suit under CPC.
Usage
/check-jurisdiction [claim-amount] [brief-facts-including-locations]
Prompt Expansion
You are the civil-procedure-specialist agent. Analyze jurisdiction using IL-CPC-001 protocol.
JURISDICTION ANALYSIS (CPC Sections 15-20, Commercial Courts Act Section 2-7):
-
PECUNIARY JURISDICTION (Based on claim value)
- Claim Amount: ₹[specify]
- Court Fee: ₹[calculate as per state Court Fees Act - typically 2-7% ad valorem]
Forum Determination:
- If < ₹3 lakhs AND non-commercial → District Court (regular civil court)
- If ≥ ₹3 lakhs AND commercial dispute → Commercial Court (district level) OR Commercial Division (High Court if within original jurisdiction)
- If ≥ ₹3 lakhs BUT non-commercial → District Court (or High Court within original jurisdiction if very high value)
-
SUBJECT-MATTER JURISDICTION Is this a "Commercial Dispute"? (Section 2(1)(c) Commercial Courts Act)
Check if dispute arises from: □ Transactions of merchants/bankers/traders □ Commercial contracts (distribution, franchising, licensing, JV, shareholders, tech, IP with value) □ Infrastructure/construction contracts □ Export/import, carriage of goods □ Financing/banking/insurance □ Partnership (non-family) □ IT/software/e-commerce □ IP rights (with specified value)
EXCLUSIONS: □ Immovable property for exclusive residence □ Consumer disputes (go to Consumer Forum) □ Oppression & Mismanagement (Companies Act - NCLT) □ Succession/testamentary
Commercial Dispute? [Yes/No] Specified Value ≥₹3 lakhs? [Yes/No]
→ If BOTH Yes: Commercial Court/Division jurisdiction
Special Jurisdictions:
- RERA: Real estate homebuyer disputes → RERA Tribunal (concurrent with civil court)
- Consumer Forum: B2C disputes → District/State/National Consumer Commission
- Arbitration: If arbitration clause → Section 9/34/37 applications in court (Commercial Court if ≥₹3 lakhs)
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.
- 12d ago First seen · 150 lines · 1 tokens per session scan A 1a43d5d76414
check-jurisdiction is a command published in the GitHub repository shashionline/indian-law-plugin (2 stars, last pushed 7mo ago), licensed MIT. It adds 1 tokens to every session and 1,493 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to check-jurisdiction, 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.