ecosystem-intake

A workflow for reviewing curated collections of developer tools and turning promising entries into tracked decisions for a repository.

In plain words
What is it for?
Use it to inspect ecosystem lists or repository changes, record candidates in SQL, score their fit, and route follow-up work.
Why use it?
It connects source review with repository fit and backlog tracking, so interesting tools become clear adopt, adapt, or reject decisions.

Skill for Claude CodeCodex

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 skills/drvoss/everything-copilot-cli/ecosystem-intake
Any agent
npx skills add drvoss/everything-copilot-cli --skill ecosystem-intake
Clone the repo
git clone --depth 1 https://github.com/drvoss/everything-copilot-cli

Made for: Claude Code, Codex.

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,996 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.00043 $0.02996
Opus 5 $0.00022 $0.01498
Sonnet 5 $0.00009 $0.00599
Haiku 4.5 $0.00004 $0.00300

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

Security

Grade A, and why

ecosystem-intake 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 2d 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.

skills/copilot-exclusive/ecosystem-intake/SKILL.md · 319 lines

How it starts

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

Ecosystem Intake

Curated lists are only useful if they turn into decisions. This skill converts ecosystem inputs like awesome-claude-code, release notes, or community skill collections into a structured adopt / adapt / reject backlog for this repository.

Why This is Copilot-Exclusive

The value is not generic web research. The value is combining GitHub-native repository inspection with session SQL tracking in one workflow:

  • GitHub MCP or web_fetch to read the upstream list or repo state
  • SQL tables to track candidate items and triage status
  • Copilot task routing to decide whether a candidate becomes a new skill, an update, or a rejection

This makes the output actionable instead of leaving it as a loose research note.

When to Use

  • A curated list like awesome-claude-code gained new entries and you want backlog candidates
  • A monitored ecosystem repo added a new command, skill, hook, or workflow worth evaluating
  • You want to scan merged PRs or README diffs and convert them into concrete next steps
  • You need a repeatable intake process instead of ad-hoc "maybe we should copy this"

When NOT to Use

Instead of ecosystem-intake Use
Deep evidence-gathering on a broad technical topic deep-research
Translating one known external pattern into a new skill skill-creator
Choosing how to execute an already-approved task task-intake-router

Intake Outcome Categories

Each candidate should end in exactly one bucket:

Outcome Meaning
Adopt Create a new skill or workflow because the gap is real and distinct
Adapt Update an existing skill because the idea fits, but the primitive already exists here
Reject Do not add it; document why it is redundant, incompatible, or low value

Workflow

0. Load the recurring-monitoring playbook when needed

If you are setting up or revisiting an ongoing watchlist, load the reference playbook first:

Read the full file on GitHub · 319 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. 2d ago First seen · 319 lines · 43 tokens per session scan A 7af3f853c3de

Subscribe to this mod's changes

ecosystem-intake is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 2,996 once invoked, about $0.0002 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.