Plugin

indian-consumer-drafting

For every consumer counsel and medical-negligence advocate practising before India's three-tier Consumer Disputes Redressal Commissions — District Commission for claims up to ₹1 crore, State Commission for claims of ₹1 crore to ₹10 crore, and the National Consumer Disputes Redressal Commission for claims above ₹10 crore — this open-source Claude Code plugin standardises drafting under the Consumer Protection Act 2019. Case-config-aware: the parties' Commission tier, pecuniary and territorial jurisdiction, deficiency-of-service / defect-in-goods / unfair-trade-practice / product-liability character, medical-negligence anchor (Jacob Mathew, Martin F. D'Souza, Kusum Sharma, the Bolam standard), Section 69 limitation anchor, and accompanying-application set are user-supplied. Battle-tested for District Section 35 Complaints, State Section 47 originals, NCDRC Section 58 originals, Medical Negligence Complaints, Product Liability Actions under Sections 82-87, Unfair Trade Practice Complaints, Appeals under Sections 41 and 51, Revisional Applications under Section 67, and Execution under Sections 71-72. Six-agent drafting pipeline + shared consumer drafting base with the Consumer Protection Act 2019, CDRC Rules 2020, E-Commerce Rules 2020, Sale of Goods Act 1930, Indian Medical Council (Professional Conduct) Regulations 2002, New Drugs and Clinical Trials Rules 2019, Bharatiya Nagarik Suraksha Sanhita 2023, and Bharatiya Sakshya Adhiniyam 2023 encoded. The finished product is a Commission-ready complaint or appeal the chamber can sign and file across the counter 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.