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/calculate-limitation)<a href="https://agentmods.dev/commands/shashionline/indian-law-plugin/calculate-limitation"><img src="https://agentmods.dev/badge/commands/shashionline/indian-law-plugin/calculate-limitation/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/calculate-limitation"><img src="https://agentmods.dev/badge/commands/shashionline/indian-law-plugin/calculate-limitation.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.01337 |
| Opus 5 | $0.00000 | $0.00668 |
| Sonnet 5 | $0.00000 | $0.00267 |
| Haiku 4.5 | $0.00000 | $0.00134 |
Grade A, and why
calculate-limitation 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.
This is a copy
100% identical to calculate-limitation — 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/calculate-limitation - Limitation Period Calculator
Description
Calculate limitation period for filing suit under Limitation Act, 1963.
Usage
/calculate-limitation [claim-type] [relevant-dates]
Prompt Expansion
You are the civil-procedure-specialist agent. Calculate limitation period using Limitation Act, 1963.
LIMITATION PERIOD CALCULATOR:
CRITICAL LIMITATION PERIODS (Limitation Act, 1963):
-
CONTRACTS
-
Article 54: Specific Performance
- Period: 3 years
- Starting Point: Date fixed for performance, OR if no date fixed, date plaintiff has notice of refusal
- Example: Agreement to sell on Dec 31, 2020. Seller refuses. Limitation expires Dec 31, 2023.
-
Article 55: Breach of Contract (Damages)
- Period: 3 years
- Starting Point: Date of breach
- Continuous breach: From first breach (subsequent breaches don't extend)
-
Article 113: Suit for Money / Residuary
- Period: 3 years
- Starting Point: When debt becomes due/right to sue accrues
-
-
INJUNCTIONS
-
Article 58: Perpetual Injunction
- Period: 3 years
- Starting Point: Date of breach (negative covenant violation)
-
Article 59: Rescission of Contract
- Period: 3 years
- Starting Point: Date plaintiff has knowledge of fraud, mistake, undue influence, misrepresentation, coercion
-
-
APPEALS
- Section 96 CPC: First Appeal
- Period: 90 days from decree
- Section 100 CPC: Second Appeal
- Period: 90 days from first appellate decree
- Section 115 CPC: Revision
- Period: 90 days
- Order 47 CPC: Review
- Period: 30 days from decree/order (60 days if new evidence)
- Section 96 CPC: First Appeal
-
EXECUTION
- Article 136: Execution of Decree
- Period: 12 years from date decree becomes enforceable
- Article 136: Execution of Decree
EXTENSIONS AND EXCLUSIONS:
Section 5: Condonation of Delay
- Court may condone delay if "sufficient cause" shown
- Sufficient cause: Bona fide reasons (illness, absence from India, legal disability)
- NOT sufficient: Negligence, laches, financial difficulties, ignorance of law
- ⚠️ Does NOT apply to appeals beyond 90 days in many cases
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 · 143 lines · 1 tokens per session scan A 50635c14e5a4
calculate-limitation is a command published in the GitHub repository shashionline/indian-law-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 1 tokens to every session and 1,337 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 calculate-limitation, 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.