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/danielraffel/generous-corp-marketplaceWrote 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/commands/danielraffel/generous-corp-marketplace/status)<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/status"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/status/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/commands/danielraffel/generous-corp-marketplace/status"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/status.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.00005 | $0.00851 |
| Opus 5 | $0.00003 | $0.00426 |
| Sonnet 5 | $0.00001 | $0.00170 |
| Haiku 4.5 | $0.00001 | $0.00085 |
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 9d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chainer: Chain Status
Display currently running chains and recently completed chains.
User Communication: Be concise. Show status directly without "Let me check..." narration.
Step 1: Read State File
Check for the chainer state file at .claude/chainer-state.json.
If the file doesn't exist, display:
No chains have been run yet.
Use /chainer:list to see available chains
Use /chainer:run <chain-name> to execute a chain
Step 2: Parse State
The state file format:
{
"running_chains": [
{
"chain": "plan-and-implement",
"started": "2025-01-05T10:30:00Z",
"cwd": "~/worktrees/oauth",
"current_step": 2,
"total_steps": 2,
"step_name": "implement",
"pid": 12345
}
],
"completed_chains": [
{
"chain": "plan-only",
"started": "2025-01-05T09:00:00Z",
"completed": "2025-01-05T09:15:00Z",
"cwd": "~/worktrees/billing",
"success": true
}
]
}
Step 3: Check Process Status
For each running chain:
- Check if the process (PID) is still alive using
ps -p <pid> - If not alive, move it to completed_chains with success=false
- Update the state file
Step 4: Display Status
Format output like this:
┌─────────────────────────────────────────┐
│ Chainer Status │
├─────────────────────────────────────────┤
│ Running Chains (1) │
│ │
│ 🔄 plan-and-implement (oauth) │
│ Step 2/2: implement │
│ Directory: ~/worktrees/oauth │
│ Running: 10 min │
│ PID: 12345 │
├─────────────────────────────────────────┤
│ Recently Completed (3) │
│ │
│ ✅ plan-only (billing) │
│ Completed 5 min ago │
│ Duration: 15 min │
│ Directory: ~/worktrees/billing │
│ │
│ ✅ implement-only (payments) │
│ Completed 1 hour ago │
│ Duration: 45 min │
│ Directory: ~/worktrees/payments │
│ │
│ ❌ plan-and-implement (subscriptions) │
│ Failed 2 hours ago │
│ Duration: 30 min │
│ Directory: ~/worktrees/subscriptions │
└─────────────────────────────────────────┘
💡 Tip: Recently completed shows last 10 chains
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.
- 9d ago First seen · 121 lines · 5 tokens per session scan A 3938b0320591
status is a command published in the GitHub repository danielraffel/generous-corp-marketplace (11 stars, last pushed 10d ago), licensed MIT. It adds 5 tokens to every session and 851 once invoked, about $0.0000 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-30.
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.