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 skills add Jamie-BitFlight/claude_skills --skill ecosystem-researchgit clone --depth 1 https://github.com/Jamie-BitFlight/claude_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/skills/jamie-bitflight/claude_skills/ecosystem-research)<a href="https://agentmods.dev/skills/jamie-bitflight/claude_skills/ecosystem-research"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/ecosystem-research/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/jamie-bitflight/claude_skills/ecosystem-research"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/ecosystem-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 108 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00103 | $0.00977 |
| Opus 5 | $0.00051 | $0.00489 |
| Sonnet 5 | $0.00021 | $0.00195 |
| Haiku 4.5 | $0.00010 | $0.00098 |
Grade A, and why
ecosystem-research 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ecosystem Research
Scope
Research target received from orchestrator:
$ARGUMENTS
Confirm the library/protocol/feature and the specific behavior or compatibility concern before proceeding. If either is absent or ambiguous, state the gap and stop.
Step 1 — GitHub Issues and Discussions
Search the primary repository's issue tracker and discussion board for real-world reports.
Search terms to apply (adapt to the library name and feature):
"doesn't work with","not supported","not compatible""workaround for","gotcha","unexpected behavior""error"+ feature name- Changelog entries referencing the feature (look for
fix:,breaking:prefixes)
For each finding: record the issue or discussion URL, a one-sentence summary of the report, and whether it was resolved.
Step 2 — Client / Host Compatibility
Identify which clients, hosts, or consumers support this feature.
Look for:
- Explicit support statements in official docs (cite URL + access date)
- Issue reports naming specific clients as broken, partial, or missing
- Test matrices or compatibility tables in the repository
Record per-client status as one of: supported, partial, unsupported, unknown. Every status requires an evidence source — do not infer.
Step 3 — Community Patterns
Identify what approaches the community has converged on.
Look for:
- Repeated workarounds appearing across multiple issues or threads
- Alternative implementations recommended by maintainers or frequent contributors
- Patterns that replaced a broken original approach (check changelogs for deprecation notices)
Cite each pattern with at least one source URL. Do not describe a pattern as "common" without at least two independent sources.
Step 4 — Real-World Gotchas
Identify what surprised users — content that is NOT in official docs but IS in issue threads, discussions, blog posts, or changelogs.
Signals to look for:
- Maintainer corrections to user assumptions in issue comments
- Changelog entries for unexpected behavioral changes (not just new features)
- Documentation PRs that added a warning section — the warning was added because someone was burned
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.
- 6d ago First seen · 110 lines · 103 tokens per session scan A c6664887c99f
ecosystem-research is a skill published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed today), licensed MIT. It adds 103 tokens to every session and 977 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…