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.
npx agentmods add commands/agirails/claude-plugin/statusgit clone --depth 1 https://github.com/agirails/claude-pluginWhat 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 | $0.00017 | $0.00967 |
| Opus 5 | $0.00009 | $0.00483 |
| Sonnet 5 | $0.00003 | $0.00193 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade A, and why
status 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 yesterday.
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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/agirails:status
Check transaction status and see what actions are available.
What This Command Does
- Get transaction ID (from argument or ask)
- Show status dashboard with current state
- Display available actions based on state and caller role
- Show timing information (deadline, dispute window)
Step-by-Step Instructions
Step 1: Get Transaction ID
If provided as argument, validate format.
If not provided, ask:
"Enter the transaction ID (0x...):"
Or offer to list recent:
"Show recent transactions?"
Options: [Yes - List last 5] [No - Enter ID manually]
Step 2: Validate Transaction ID
Format: 0x + 64 hexadecimal characters
If invalid:
"Invalid transaction ID format. Expected: 0x followed by 64 hex characters.
Example: 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"
Step 3: Generate Status Code
TypeScript:
const status = await client.basic.checkStatus('0x...');
console.log('State:', status.state);
console.log('Can accept:', status.canAccept);
console.log('Can complete:', status.canComplete);
console.log('Can dispute:', status.canDispute);
Step 4: Display Status Dashboard
┌─────────────────────────────────────────────────────────────┐
│ TRANSACTION STATUS │
├─────────────────────────────────────────────────────────────┤
│ ID: 0xabc123...def456 │
│ State: DELIVERED (awaiting release) │
│ │
│ Progress: │
│ INITIATED → COMMITTED → IN_PROGRESS → DELIVERED → [ ] SETTLED │
│ [x] [x] [x] [*] │
│ │
│ Details: │
│ Requester: 0xReq...123 │
│ Provider: 0xPro...456 │
│ Amount: 100000000 (USDC wei) │
│ │
│ Timing: │
│ Created: 2025-12-27 10:30 UTC │
│ Delivered: 2025-12-27 14:45 UTC │
│ Deadline: 2025-12-28 10:30 UTC │
│ │
│ Dispute Window: 47h 15m remaining │
│ Auto-settles in: 47h 15m (if no dispute) │
└─────────────────────────────────────────────────────────────┘
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.
- yesterday First seen · 139 lines · 17 tokens per session scan A 39c32b1a1b06
status is a command published in the GitHub repository agirails/claude-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 967 once invoked, about $0.0001 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.