check-writ

check-writ is a command for Claude Code from edenbuilds/arya-ai. It costs 55 tokens per session (2,430 once invoked), scanned A, original, MIT.

A tool that evaluates whether an Indian writ petition is suitable for challenging government action. A writ petition asks a High Court or the Supreme Court to review a public authority's decision or failure to act.

In plain words
What is it for?
Use it for disputes involving government refusals, unlawful orders, failure to perform mandatory duties, illegal detention, or someone improperly holding public office.
Why use it?
It helps determine whether the respondent is a public authority, whether the applicant has standing, whether another remedy must be tried first, and which type of writ fits the case.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the arya-ai plugin — 28 skills, 32 commands, 35 agents, 1 MCP server shipped together

Install

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.

agentmods
npx agentmods add commands/edenbuilds/arya-ai/check-writ
Clone the repo
git clone --depth 1 https://github.com/edenbuilds/arya-ai

Made for: Claude Code.

Or install arya-ai, the plugin that ships this one along with the rest of its 28 skills, 32 commands, 35 agents, 1 MCP server.

Wrote 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.

agentmods badge for check-writ

README.md
[![agentmods](https://agentmods.dev/badge/commands/edenbuilds/arya-ai/check-writ.svg)](https://agentmods.dev/commands/edenbuilds/arya-ai/check-writ)
Your own site
<a href="https://agentmods.dev/commands/edenbuilds/arya-ai/check-writ"><img src="https://agentmods.dev/badge/commands/edenbuilds/arya-ai/check-writ.svg" alt="Measured on agentmods" height="20"></a>
Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,430 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.02430
Opus 5 $0.00028 $0.01215
Sonnet 5 $0.00011 $0.00486
Haiku 4.5 $0.00006 $0.00243

Measured 6d ago against content hash eb89419da4fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

check-writ 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 6d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

commands/check-writ.md · 318 lines

How it starts

The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/check-writ - Writ Petition Viability Checker

Command Purpose

Comprehensive writ petition viability analysis tool that assesses whether filing a writ petition (mandamus, certiorari, prohibition, habeas corpus, quo warranto) under Article 226 (High Court) or Article 32 (Supreme Court) is appropriate for your case.

How It Works

This command launches the writ-petition-analyzer skill through an interactive Q&A session that systematically evaluates:

  1. Whether respondent is "State" (Article 12)
  2. Your locus standi (standing to file)
  3. Alternative remedy requirements
  4. Grounds for judicial review
  5. Appropriate writ type
  6. Likelihood of success
  7. Strategic recommendations

When to Use

  • Government authority denied your application/permission
  • Government order you want to challenge
  • Government refusing to perform mandatory duty
  • Illegal detention by authorities
  • Unauthorized person holding public office
  • Need urgent judicial intervention against government action

Usage

/check-writ

OR with case context:

/check-writ Municipality denied my building permission without valid reason
/check-writ Passport approved but not issued for 60 days

Workflow

When you invoke /check-writ, I will conduct systematic legal analysis:

Step 1: Case Facts Gathering

I'll ask you structured questions:

Q1: What is the government action/inaction you want to challenge?

  • Order passed (denying permission, rejecting application, etc.)?
  • Inaction (duty not performed, service not delivered)?
  • Detention?
  • Appointment to public office?

Q2: Which authority is involved?

  • Central/State Government department?
  • Local body (municipality, panchayat)?
  • PSU, statutory corporation?
  • Private entity?

Q3: When did this happen?

  • Date of impugned order (if challenging an order)
  • Date when duty should have been performed
  • How long ago? (Check for laches/delay)

Q4: What did you do before approaching court?

  • Filed application/representation?
  • Pursued departmental appeal/tribunal?
  • Filed RTI, CPGRAMS grievance?
  • Sent legal notice?

Read the full file on GitHub · 318 lines

Changes

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.

  1. 6d ago First seen · 318 lines · 55 tokens per session scan A eb89419da4fd

Subscribe to this mod's changes

check-writ is a command published in the GitHub repository edenbuilds/arya-ai (3 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 2,430 once invoked, about $0.0003 per session on Opus 5. 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.