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/data-wise/claude-plugins/ecosystem-healthgit clone --depth 1 https://github.com/Data-Wise/claude-pluginsWrote 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/data-wise/claude-plugins/ecosystem-health)<a href="https://agentmods.dev/commands/data-wise/claude-plugins/ecosystem-health"><img src="https://agentmods.dev/badge/commands/data-wise/claude-plugins/ecosystem-health.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 | $0.00000 | $0.00710 |
| Opus 5 | $0.00000 | $0.00355 |
| Sonnet 5 | $0.00000 | $0.00142 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
ecosystem-health 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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ecosystem Health Check
You are conducting a comprehensive health check of the MediationVerse R package ecosystem.
MediationVerse Packages
| Package | Path | Purpose |
|---|---|---|
| medfit | ~/R-packages/active/medfit | Foundation (fitting, extraction, bootstrap) |
| probmed | ~/R-packages/active/probmed | P_med probabilistic effect size |
| rmediation | ~/R-packages/active/rmediation | Confidence intervals (PRODCLIN) |
| medrobust | ~/R-packages/active/medrobust | Sensitivity analysis |
| medsim | ~/R-packages/active/medsim | Simulation infrastructure |
| mediationverse | ~/R-packages/active/mediationverse | Meta-package |
Health Check Process
Step 1: Package Status
For each package, check:
- R CMD check status (use r_check tool if available)
- Test coverage (aim for >80%)
- Documentation completeness
- DESCRIPTION version and dependencies
Step 2: Dependency Analysis
- Check inter-package dependencies
- Identify version conflicts
- Verify dependency chain is correct:
medfit (foundation) ├── probmed (depends on medfit) ├── rmediation (standalone, may use medfit) ├── medrobust (depends on medfit) └── medsim (depends on medfit, probmed) mediationverse (imports all)
Step 3: API Consistency
- Are S7 class definitions consistent across packages?
- Do function signatures follow conventions?
- Is documentation style consistent?
Step 4: Test Integration
- Do cross-package workflows work?
- Are integration tests passing?
Step 5: Documentation
- Are pkgdown sites building?
- Is the ecosystem navigation correct?
- Are vignettes up to date?
Output Format
## MediationVerse Ecosystem Health Report
**Date**: [Date]
### Summary Dashboard
| Package | R CMD Check | Coverage | Docs | Version |
|---------|-------------|----------|------|---------|
| medfit | ✓/⚠/✗ | XX% | ✓/⚠ | X.Y.Z |
| probmed | ... | ... | ... | ... |
| ... | ... | ... | ... | ... |
### Overall Status: 🟢 Healthy / 🟡 Needs Attention / 🔴 Issues
### Detailed Findings
#### medfit
- **Status**: [Summary]
- **Issues**: [List any problems]
- **Action needed**: [Recommended fixes]
[Repeat for each package]
### Dependency Graph
[ASCII or description of current dependency state]
### Cross-Package Issues
[Any issues that span multiple packages]
### Recommendations
1. **Immediate**: [Urgent fixes]
2. **Short-term**: [Should address soon]
3. **Long-term**: [Future improvements]
### Next Steps
[Specific action items with priorities]
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.
- 4d ago First seen · 100 lines · 0 tokens per session scan A c4412fe28a37
ecosystem-health is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 710 tokens. 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
git
Git operations with intelligent commit messages and workflow optimization.
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.