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/commercial-court-check)<a href="https://agentmods.dev/commands/shashionline/indian-law-plugin/commercial-court-check"><img src="https://agentmods.dev/badge/commands/shashionline/indian-law-plugin/commercial-court-check/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/commercial-court-check"><img src="https://agentmods.dev/badge/commands/shashionline/indian-law-plugin/commercial-court-check.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.00000 | $0.01345 |
| Opus 5 | $0.00000 | $0.00673 |
| Sonnet 5 | $0.00000 | $0.00269 |
| Haiku 4.5 | $0.00000 | $0.00135 |
Grade A, and why
commercial-court-check 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 commercial-court-check — 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: Determine if dispute qualifies for Commercial Court jurisdiction under Commercial Courts Act, 2015. argument-hint: [brief-dispute-description] [amount-involved]
/commercial-court-check - Commercial Dispute Classification
Description
Determine if dispute qualifies for Commercial Court jurisdiction under Commercial Courts Act, 2015.
Usage
/commercial-court-check [brief-dispute-description] [amount-involved]
Prompt Expansion
You are the commercial-litigation-specialist agent. Analyze using IL-COMMERCIAL-001 protocol.
COMMERCIAL DISPUTE CLASSIFICATION:
TWO-PART TEST:
- Specified Value ≥ ₹3 lakhs?
- "Commercial Dispute" under Section 2(1)(c)?
Both must be YES for Commercial Court jurisdiction.
PART 1: SPECIFIED VALUE CALCULATION (Section 12)
User's Claim Amount: ₹[specify]
Calculation Method:
- If transaction has consideration → Value = consideration stated in contract
- If no consideration → Market value of subject matter
- If multiple reliefs from same transaction → Aggregate all
- Counterclaim value NOT added (each side's claim evaluated separately)
Specified Value: ₹[calculate] ≥ ₹3 lakhs? [Yes / No]
If NO → Regular Civil Court (not Commercial Court) If YES → Proceed to Part 2
PART 2: "COMMERCIAL DISPUTE" DEFINITION (Section 2(1)(c))
Does dispute arise out of:
Category A: Commercial Transactions □ Transactions of merchants/bankers/financiers/traders □ Purchase/sale of goods (mercantile activity) □ Mercantile agency □ Factoring □ Mercantile documents (bills of exchange, promissory notes)
Category B: Commercial Contracts □ Trade and commerce contracts □ Distribution agreements □ Licensing agreements □ Franchising □ Consulting □ Joint ventures □ Shareholders agreements □ Subscription/investment agreements □ Technology development □ Intellectual property rights (with Specified Value)
Category C: Infrastructure & Construction □ EPC (Engineering, Procurement, Construction) contracts □ Sub-contracting □ Concession agreements □ Power purchase agreements
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 · 200 lines · 0 tokens per session scan A 75358198c91c
commercial-court-check is a command published in the GitHub repository shashionline/indian-law-plugin (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,345 tokens. A static security scan graded it A with 0 findings. It is 100% identical to commercial-court-check, 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.