Plugin

indian-mact-drafting

For every advocate practising before India's Motor Accident Claims Tribunals — the tribunal-tier where every road accident in India ultimately lands for compensation — and before the High Court on Section 173 appeals and the Magistrate's Court on the rash / negligent-driving trial under BNSS 2023, this open-source Claude Code plugin standardises the full motor-accident litigation surface. Case-config and state-config-aware: forum (MACT of the territorial district, High Court for Section 173 appeal, Magistrate Court for the rash / negligent-driving prosecution, Collector for Section 174 recovery), accident-trigger date, claimant composition (legal representatives of the deceased / injured claimant / property-damage claimant), vehicle particulars, FIR particulars, insurer particulars, Sarla Verma + Pranay Sethi multiplier inputs, and State Motor Vehicles Rules variations are user-supplied. Battle-tested for Section 166 fault-based claims, Section 164 lump-sum claims (post-2019 amendment, replacing Section 163A), Section 161 solatium / hit-and-run claims, Section 147 / 149 third-party insurance pleadings, interim compensation applications, Section 173 appeals to the High Court, claim-award execution, Employees' Compensation Act 1923 claims, rash / negligent-driving defence under BNSS 2023, and Section 174 recovery as arrears of land revenue. Six-agent drafting pipeline + shared MACT drafting base with the Motor Vehicles Act 1988 (as amended 2019), Central Motor Vehicles Rules 1989, applicable State MV Rules, Employees' Compensation Act 1923, BNS / BNSS / BSA 2023, the Sarla Verma multiplier doctrine, and the Pranay Sethi constitution-bench future-prospects reform encoded. The finished product is a Tribunal-ready claim petition or appeal the team can lodge the same day.

• Published source
• Repository

Analysed

12 October 2026

Last observed

13 October 2026

What the code does

What does this mean?

These are capabilities our static analysis found in the latest published version. They describe what the code can do, not whether it is malicious: many tools need shell access or the network to do their job. Use them to decide what to check before installing.

Static analysis found none of the capabilities we track, such as shell commands, network requests or file writes, in the latest version.

Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.

This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.