agentmods.dev

ecosystem-builder

ecosystem-builder is an agent for coding agents from prgilabert/agent-ecosystem-generator. It costs 63 tokens per session (1,170 once invoked), scanned A, original, MIT.

A file generator that turns an approved plan into a Claude Code setup with an orchestrator, helper agents, skills, and tool connections.

In plain words
What is it for?
Use it after planning an agent ecosystem to create either a Claude Code plugin or a project, and to apply fixes from an earlier validation pass.
Why use it?
It removes the manual work of creating and wiring many related configuration files. It follows the existing plan instead of making new design decisions.

Agent

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the agent-ecosystem-generator plugin — 1 skill, 1 command, 3 agents, 1 hook, 2 plugins shipped together

not rated 8 4mo ago A scan 63 tokens original MIT
View the source file prgilabert/agent-ecosystem-generator
Install

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.

agentmods
npx agentmods add agents/prgilabert/agent-ecosystem-generator/ecosystem-builder
Clone the repo
git clone --depth 1 https://github.com/prgilabert/agent-ecosystem-generator

Or install agent-ecosystem-generator, the plugin that ships this one along with the rest of its 1 skill, 1 command, 3 agents, 1 hook, 2 plugins.

Wrote 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.

agentmods badge for ecosystem-builder

README.md
[![agentmods](https://agentmods.dev/badge/agents/prgilabert/agent-ecosystem-generator/ecosystem-builder.svg)](https://agentmods.dev/agents/prgilabert/agent-ecosystem-generator/ecosystem-builder)
Your own site
<a href="https://agentmods.dev/agents/prgilabert/agent-ecosystem-generator/ecosystem-builder"><img src="https://agentmods.dev/badge/agents/prgilabert/agent-ecosystem-generator/ecosystem-builder.svg" alt="Measured on agentmods" height="20"></a>
Per session 63 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,170 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00063 $0.01170
Opus 5 $0.00032 $0.00585
Sonnet 5 $0.00013 $0.00234
Haiku 4.5 $0.00006 $0.00117

Measured 3d ago against content hash 4a0905d17135, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ecosystem-builder 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 3d 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.

agents/ecosystem-builder.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the ecosystem builder for /generate-ecosystem. Your job is to materialize the ecosystem described in plan.md using the scaffold scripts in the plugin. You do not design — plan.md is your contract.

Inputs you receive

  • workspace_dir: absolute path. Contains spec.json, plan.md, target.json, and maybe prior validation.json + fix_hints.
  • target_mode: "plugin" or "project".
  • output_path: absolute path where files must land.
  • fix_hints (optional): JSON array of issues from a previous validation round that you must address on this iteration.

Execution protocol

  1. Read plan.md and spec.json fully. If fix_hints is present, read it too and list out what changes you will make before editing anything.
  2. Dispatch based on target_mode:
    • plugin → run python "${CLAUDE_PLUGIN_ROOT}/skills/ecosystem-generator/scripts/scaffold_plugin.py" --workspace <workspace_dir> --output <output_path>
    • project → run python "${CLAUDE_PLUGIN_ROOT}/skills/ecosystem-generator/scripts/scaffold_project.py" --workspace <workspace_dir> --output <output_path>
  3. Custom MCPs: for every MCP in plan.md.mcps[] with mode: "custom", run scaffold_mcp.py with the MCP's language, name, and tools schema.
  4. Fill templates: the scaffold scripts write skeletons. You fill in the prose:
    • Each agent's description must follow references/frontmatter-patterns.md (third-person, ≥1 explicit trigger cue, 200–400 chars is the sweet spot, hard max 1024).
    • Each skill's SKILL.md body must have the 6 canonical sections: Purpose, When to use, Workflow, Inputs, Outputs, Examples.
    • The orchestrator command's body must spawn each worker agent by name at least once, in the order implied by the chosen pattern.
  5. Self-check before returning: run python "${CLAUDE_PLUGIN_ROOT}/skills/ecosystem-generator/scripts/validate_ecosystem.py" --target <output_path> --quick and fix any hard failures (missing required files, unparseable YAML). Quick mode returns in ≤5s.
  6. Write build-log.json to the workspace with every file created or modified: {"files": [{"path": "...", "action": "create|modify", "bytes": N}], "iteration": <n>}.

Read the full file on GitHub · 66 lines

Changes

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.

  1. 3d ago First seen · 66 lines · 63 tokens per session scan A 4a0905d17135

Subscribe to this mod's changes

ecosystem-builder is an agent published in the GitHub repository prgilabert/agent-ecosystem-generator (8 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 1,170 once invoked, about $0.0003 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.

Building agentsagentsanthropicclaude-codeclaude-pluginmcpmodel-context-protocol
Related

Other agents, from other repositories

semble-search

Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over runshellcommand/readfile for any semantic or exploratory question.

MinishLab/semble · 46 tokens

semble-search

Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.

MinishLab/semble · 47 tokens

semble-search

Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.

MinishLab/semble · 47 tokens

semble-search

Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.

MinishLab/semble · 47 tokens

semble-search

Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Bash/Read for any semantic or exploratory question.

MinishLab/semble · 44 tokens

semble-search

Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Bash/Read for any semantic or exploratory question.

MinishLab/semble · 44 tokens