Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add danielraffel/generous-corp-marketplace/plugin install chainerWrote 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/run)<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/run"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/run.svg" alt="Measured on agentmods" 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.00013 | $0.03892 |
| Opus 5 | $0.00006 | $0.01946 |
| Sonnet 5 | $0.00003 | $0.00778 |
| Haiku 4.5 | $0.00001 | $0.00389 |
Grade A, and why
run 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 8d 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 — 600 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chainer: Run Chain
Execute a configured chain by name.
User Communication Guidelines
CRITICAL: Keep status updates concise and user-focused. Avoid verbose explanations.
Status Line Pattern
Use this format for all status updates:
⏺ <What you're doing>... <why it matters OR what it enables>
Good examples:
- ⏺ Checking Chainer config for your Galaxian game...
- ⏺ No chain specified. Selecting best workflow based on your request...
- ⏺ Using defaults (no local config found).
Bad examples (avoid these):
- ⏺ I'll help you run the chainer command to develop a Galaxian-style game. Let me start by reading the configuration files...
- ⏺ Now let me parse the arguments. Based on the user's request, they want to develop...
What to Show vs Hide
ALWAYS SHOW:
- Chain being executed
- Critical decisions (which chain chosen, why)
- Plugin execution (feature-dev starting, ralph-loop running)
- Errors that require user action
- Question prompts (interactive UI)
- Final results
HIDE/SUPPRESS:
- Missing optional config files (just say "Using defaults")
- Successful file reads (unless debugging)
- Internal parsing/validation steps
- Reasoning about obvious things
- Tool results that worked as expected
Error Handling
For missing optional files:
⏺ Looking for local config... none found. Using defaults.
NOT:
⏺ Read(.claude/chainer.local.md)
⎿ Error reading file
⏺ Read(~/.claude/chainer.local.md)
⎿ Error reading file
Decision Communication
Pattern: Observation → Decision → Action (one line)
Good:
⏺ No chain specified. This looks like a frontend design task—using frontend-design workflow.
Bad:
⏺ I see the issue - the user provided a detailed description but didn't specify which chain. Looking more closely, this seems like it would be better suited for frontend-design rather than plan-and-implement. Let me use frontend-design directly.
Step 1: Parse Arguments
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.
- 8d ago First seen · 600 lines · 13 tokens per session scan A a5c46a92c685
run is a command published in the GitHub repository danielraffel/generous-corp-marketplace (11 stars, last pushed 9d ago), licensed MIT. It adds 13 tokens to every session and 3,892 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-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.