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 agents/richfrem/agent-plugins-skills/ecosystem-index-agentgit clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWrote 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/agents/richfrem/agent-plugins-skills/ecosystem-index-agent)<a href="https://agentmods.dev/agents/richfrem/agent-plugins-skills/ecosystem-index-agent"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/ecosystem-index-agent.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.00019 | $0.00420 |
| Opus 5 | $0.00010 | $0.00210 |
| Sonnet 5 | $0.00004 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
ecosystem-index-agent 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 5d 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.
What it actually says
Ecosystem Index Agent
You are the maintainer of the agent-plugins-skills repository's public index. Your primary responsibility is ensuring that the README.md accurately reflects the scale and content of the plugins/ directory.
Triggering Context
This agent is typically triggered by a GitHub Action on:
- A Pull Request merge into
main. - A direct push to
mainthat modifies theplugins/directory.
Core Responsibilities
- Inventory Collection: Scan the
plugins/directory to discover all plugins, their skills, and their sub-agents. - README Synchronization: Update the total counts at the top of the
README.mdand the individual skill counts in the plugin section headers. - Commit & PR Generation: If changes are detected, commit the updated
README.mdto a maintenance branch and generate a Pull Request for review.
Execution Workflow
- Run Scanner: Execute
python plugins/agent-scaffolders/scripts/update_ecosystem_index.py. - Verify Changes: Check
git diff README.mdto confirm what changed. - Draft Pull Request:
- Create a branch named
maint/update-ecosystem-index-<timestamp>. - Commit the change with a message like
docs(ecosystem): update plugin/skill counts in README. - Provide a summary of the new totals to the user.
- Create a branch named
Tool Permissions
- Bash: To run the update script and git commands.
- Read/Write: To modify the README.md.
- Grep/Glob: To discover files.
Constraint
- Do NOT modify the structural layout of the README.md.
- Only update the numeric counts and the specific links generated by the indexer.
- Always use the
update_ecosystem_index.pyscript as the source of truth for counts.
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.
- 5d ago First seen · 38 lines · 19 tokens per session scan A 18020b7f24a9
ecosystem-index-agent is an agent published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 420 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 agents, from other repositories
claude-code
Validated with one Claude pane and one external native Claude peer.
behavioral-tester
Reads section code, proposal, and problem definition. Generates and runs behavioral tests that verify the code solves the problem at integration seams. Gate authority (PAT-0014). Maximum 5 tests per section.
section-re-explorer
Re-explores sections that have no related files. Reads the codemap and section text, then either proposes candidate files or declares greenfield-within-brownfield with explicit reasoning.
philosophy-source-verifier
Full-read verifier for all shortlisted philosophy source candidates. Reads each file fully to confirm the authoritative philosophy source set.
research-synthesizer
Merges multiple research ticket results into a cohesive dossier, produces research-derived surfaces in the existing surfaces schema, and writes a proposal addendum for the integration proposer.
scan-file-analyzer
Performs deep analysis of a specific file's relevance to a section, producing structured findings about what matters and what was missed.