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/check-deps)<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/check-deps"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/check-deps/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/check-deps"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/check-deps.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.00006 | $0.01319 |
| Opus 5 | $0.00003 | $0.00660 |
| Sonnet 5 | $0.00001 | $0.00264 |
| Haiku 4.5 | $0.00001 | $0.00132 |
Grade A, and why
check-deps 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 10d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Dependencies Command
Verify plugin installation status for Chainer chains.
Usage
/chainer:check-deps [chain-name]
What It Does
- Checks if required plugins are installed for a chain
- Shows which plugins are missing
- Provides exact installation commands
- Can check a specific chain or all built-in chains
Examples
Check Specific Chain
/chainer:check-deps plan-and-implement
Output:
Dependency Check: plan-and-implement
Required plugins:
✅ feature-dev (installed)
✅ ralph-loop (installed)
Status: ✅ Ready to run
Check All Chains
/chainer:check-deps
Output:
Built-in Chains Dependency Status:
plan-only:
✅ feature-dev (installed)
Status: ✅ Ready
implement-only:
✅ ralph-loop (installed)
Status: ✅ Ready
plan-and-implement:
✅ feature-dev (installed)
❌ ralph-loop (not installed)
Status: ❌ Cannot run (missing 1 plugin)
worktree-plan-implement:
✅ worktree-manager (installed)
✅ feature-dev (installed)
❌ ralph-loop (not installed)
Status: ❌ Cannot run (missing 1 plugin)
Instructions for Claude
When user invokes this command:
Step 1: Parse Arguments
const args = parseArguments();
const chainName = args[0]; // Optional - if omitted, check all chains
Step 2: Load Registry
Read the plugin registry:
const registryPath = '${CLAUDE_PLUGIN_ROOT}/registry/plugins.yaml';
const registryContent = Read(registryPath);
const registry = parseYaml(registryContent);
If registry doesn't exist:
❌ Plugin registry not found
Expected location: ${CLAUDE_PLUGIN_ROOT}/registry/plugins.yaml
This is required for dependency checking.
Step 3: Load Installed Plugins
const installedPath = '~/.claude/plugins/installed_plugins.json';
const installedData = JSON.parse(Read(installedPath));
If file doesn't exist, treat as no plugins installed.
Step 4: Check Dependencies
If chain name provided (specific chain):
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.
- 10d ago First seen · 261 lines · 6 tokens per session scan A 504ae1ec12e9
check-deps is a command published in the GitHub repository danielraffel/generous-corp-marketplace (11 stars, last pushed 11d ago), licensed MIT. It adds 6 tokens to every session and 1,319 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.
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.