Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/drvoss/everything-copilot-clinpx agentmods add skills/drvoss/everything-copilot-cli/ecosystem-intakeWrote 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/skills/drvoss/everything-copilot-cli/ecosystem-intake)<a href="https://agentmods.dev/skills/drvoss/everything-copilot-cli/ecosystem-intake"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/ecosystem-intake/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/skills/drvoss/everything-copilot-cli/ecosystem-intake"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/ecosystem-intake.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.03001 |
| Opus 5.5 | $0.00017 | $0.01200 |
| Sonnet 5.5 | $0.00009 | $0.00600 |
| Haiku 4.5 | $0.00004 | $0.00300 |
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 today.
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 — 320 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_fetchto 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-codegained 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:
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.
- today Changed · +1 lines 2c998efcdfef
- yesterday Changed dbead873a418
- 1mo ago First seen · 319 lines · 43 tokens per session scan A 7af3f853c3de
ecosystem-intake is a skill published in the GitHub repository drvoss/everything-copilot-cli (49 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 3,001 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
speckit-workflow
Manage and run Spec Kit automation workflows via specify workflow. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use…
session-statusline
Manage only the current session's active statusline pills and clear entries without deleting work or changing enabled components. USE FOR: name this session, custom statusline name, label this terminal session, rename session label, clear session name, clear statusline, clear footer pills, remove a PR pill, remove an…
ask-navigator
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding, not building: it…
omc-ado-sprint
Azure DevOps sprint planning: manage iterations, check team capacity, groom the backlog, and assign work to sprints. Not for work item triage (omc-ado-triage), PR review, pipeline management, or GitHub repos (omc-gh-project).
omc-ado-triage
Triage Azure DevOps: board status, untriaged work items, active work, open PRs, pipeline failures, and security alerts for a project health overview. Not for sprint planning, PR code review, or GitHub repos (omc-gh-triage).
launch-command
Launch orchestration and readiness assessment engine with cross-functional workstream tracking and go/no-go gates. Use when: launch readiness, launch checklist, launch orchestration, go no go, launch plan, are we ready to launch.