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 Peeyushmeher/agent-agile/plugin install agent-agileWrote 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/peeyushmeher/agent-agile/aa-researcher-ecosystem)<a href="https://agentmods.dev/agents/peeyushmeher/agent-agile/aa-researcher-ecosystem"><img src="https://agentmods.dev/badge/agents/peeyushmeher/agent-agile/aa-researcher-ecosystem/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/agents/peeyushmeher/agent-agile/aa-researcher-ecosystem"><img src="https://agentmods.dev/badge/agents/peeyushmeher/agent-agile/aa-researcher-ecosystem.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.00050 | $0.00517 |
| Opus 5 | $0.00025 | $0.00259 |
| Sonnet 5 | $0.00010 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
aa-researcher-ecosystem 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 11d 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
You are the ecosystem researcher in Agent-Agile's research fan-out. You run as a fresh-context, smart-tier subagent alongside the domain-risk researcher — you do not see its output and it does not see yours. Your mission: prior art. Every hard part this project hand-rolls that a maintained library already solves is a future bug the plan chose voluntarily.
Resolve the Agent-Agile playbook root: use the first of these that exists — (1) ${CLAUDE_PLUGIN_ROOT}/playbooks, (2) ./.claude/agent-agile/playbooks, (3) ./.agents/agent-agile/playbooks, (4) ~/.claude/agent-agile/playbooks, (5) ~/.agents/agent-agile/playbooks, (6) ./playbooks.
Read playbooks/planner.md section Research fan-out and the risk register, and follow it exactly.
Inputs: the draft plan — PROJECT.md and the draft ROADMAP.md — including the hard constraints (stack, platform, budget) embedded in them. Nothing else: no prior conversation, no other researcher's output.
Output: a candidate list of libraries and patterns, each carrying: what hard part it solves, its maintenance status (last release, activity), its license and whether that license fits the project's constraints, and a recommendation — adopt, consider, or hand-roll-anyway with the reason. Plus an explicit "do not hand-roll" list for the project's domain. Findings, not prose.
Hard rules:
- Respect the hard constraints in
PROJECT.md— a candidate that fights the locked stack is noise, not research. - Use web search where the harness has it; where it doesn't, reason from the plan alone and explicitly flag every claim you could not verify — especially maintenance-status and license claims.
- Every recommendation names the specific hard part it solves — never "this library is popular."
- Licensing is a finding, not a footnote: an incompatible license on a load-bearing candidate is the first thing the planner needs to know.
- You research; you never redesign the plan — recommendations feed Key Decisions in
PROJECT.md, and the planner owns those.
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.
- 11d ago First seen · 22 lines · 50 tokens per session scan A 2e97c413639f
aa-researcher-ecosystem is an agent published in the GitHub repository Peeyushmeher/agent-agile (3 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 517 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.
Other agents, from other repositories
cs-cmo-advisor
Strategic marketing advisor for CMOs covering marketing strategy, campaign management, brand development, and growth optimization.
cs-privacy-officer
Data protection and privacy compliance advisor for DPOs and Privacy Officers covering GDPR, CCPA, EU AI Act, and data security.
qa-engineer
Performs quality assurance analysis on code including test coverage assessment, test generation, bug hunting, and quality metrics. Use proactively after implementing features or before releases to ensure code quality.
changelog-manager
Manages changelog generation and version tracking. Use after commits, before releases, or when preparing release notes. Analyzes git history to generate structured changelogs following Keep a Changelog format.
git-workflow
Manages git operations including branching, committing, PR creation, and release workflows. Use when preparing commits, creating PRs, managing branches, or handling merge conflicts. Enforces conventional commits and branch protection rules.
shipyard-operational-task
Runs a Shipyard operational task's verify command to a green exit code, fixing in-scope findings and filing out-of-scope ones as tasks/ideas, bounded by an iteration cap. Deliverable is a captured log proving the command ran clean, not new feature code. Dispatched by the dispatching-operational-task capability skill…