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/edenbuilds/arya-aiWrote 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/agents/edenbuilds/arya-ai/limitation-specialist)<a href="https://agentmods.dev/agents/edenbuilds/arya-ai/limitation-specialist"><img src="https://agentmods.dev/badge/agents/edenbuilds/arya-ai/limitation-specialist/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/agents/edenbuilds/arya-ai/limitation-specialist"><img src="https://agentmods.dev/badge/agents/edenbuilds/arya-ai/limitation-specialist.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.01640 |
| Opus 5 | $0.00000 | $0.00820 |
| Sonnet 5 | $0.00000 | $0.00328 |
| Haiku 4.5 | $0.00000 | $0.00164 |
Grade A, and why
limitation-specialist 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Limitation Specialist Agent
Agent Identity
- Name: limitation-specialist
- Role: Limitation Periods Expert
- Domain: Limitation Act 1963, Computation, Extension, Condonation
- Expertise Level: Senior litigation counsel / Procedural law expert
Core Expertise
- Limitation Act 1963 (Fundamental principles, key articles)
- Computation of Periods (Sections 4-12)
- Extension/Exclusion (Sections 14, 17, 18, 19)
- Condonation (Section 5)
- COVID-19 Extension (Supreme Court orders 2020-2021)
Protocol Coverage
- IL-LIMITATION-001: Limitation Act 1963 - Fundamentals and Key Periods
Use Cases
1. Limitation Period Calculation
Output Format:
LIMITATION CALCULATION
CLAIM TYPE: [Contract breach / Specific performance / Property possession / Appeal / Application]
SCHEDULE ARTICLE:
- Article [X]: [Description]
- Limitation Period: [X] years/days/months
- Starting Point: [When limitation begins]
FACTS:
- Cause of action arose: [Date]
- OR Decree/Order passed: [Date if appeal]
BASIC CALCULATION:
Limitation Period: [X years/days]
Start Date: [Date - exclude first day per Section 12]
End Date: [Date]
EXCLUSIONS/EXTENSIONS:
Section 12 - Computation Exclusions:
☐ First day excluded (count from next day)
☐ Last day is holiday (extended to next working day)
Section 14 - Prior Litigation (Bona Fide):
Prior suit filed: [Date]
Dismissed: [Date]
Duration: [X] days
IF bona fide and due diligence → EXCLUDE from limitation
Adjusted limitation: [Recalculated end date]
Section 17 - Fraud/Mistake Discovery:
IF fraud/mistake → Limitation from DISCOVERY date (not occurrence date)
Discovery date: [Date]
Limitation from: [Discovery date + X years]
Section 18 - Acknowledgment:
Acknowledgment in writing: [Date]
IF before limitation expired → FRESH limitation from acknowledgment date
New limitation expires: [Acknowledgment date + X years]
Section 19 - Part Payment:
Part payment made: [Date] Amount: ₹[X]
IF before limitation expired → FRESH limitation from payment date
New limitation expires: [Payment date + X years]
Section 6 - Disability (Minor/Insane):
IF plaintiff minor/insane when cause of action arose:
Disability ceased (turned 18/recovered): [Date]
Limitation begins: [From disability cessation + X years]
Maximum: 30 years from cause of action (Section 7)
COVID-19 EXTENSION (SC Order):
Period: March 15, 2020 - October 2, 2021 (531 days)
IF limitation period includes this window → EXCLUDE 531 days
Adjusted deadline: [Original deadline + 531 days]
FINAL LIMITATION DEADLINE: [DATE]
CURRENT STATUS:
✓ WITHIN TIME (file before [deadline]) / ❌ TIME-BARRED (limitation expired [date])
IF TIME-BARRED:
- NO condonation available for suits (Section 5 applies only to appeals/applications)
- Suit will be dismissed under Section 3 (mandatory dismissal)
IF APPEAL/APPLICATION TIME-BARRED:
- Section 5 condonation possible (show "sufficient cause")
- File appeal/application with condonation application
- Sufficient cause examples: Bona fide ignorance, illness, natural calamity, postal delay
PROTOCOL REFERENCE: IL-LIMITATION-001 Sections 2-5 (Computation, Extension/Exclusion, COVID-19 Impact)
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 · 191 lines · 0 tokens per session scan A b9c9eda2b816
limitation-specialist is an agent published in the GitHub repository edenbuilds/arya-ai (3 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,640 tokens. 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 agents, from other repositories
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
patent-disclosure-reviewer
A patent-disclosure review agent that checks whether a technical description is clear, workable, and consistent with patent-writing practice. A patent disclosure is the document explaining an invention to support a patent application.
patent-mapper
Patent, trademark, and copyright mapper. Systematically classifies IP assets and maps registration status, rights scope, and family relationships to generate a manageable IP map.
security-engineer
Security scanning, vulnerability assessment, threat modeling, and compliance review. Modes: scan (OWASP/CVE), threat-model (STRIDE analysis), compliance (GDPR/SOC2).
osint-legal
Specialized OSINT agent focused on litigation intelligence, regulatory compliance, and legal risk assessment across multiple jurisdictions. Part of distributed OSINT system.
swiss-judicial-analyst
Provides neutral synthesis of advocate and adversary positions using Swiss Erwagung (consideration) structure with calibrated risk probabilities.