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 prime-radiant-inc/greenfield --skill ecosystem-analysisgit clone --depth 1 https://github.com/prime-radiant-inc/greenfieldWrote 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/prime-radiant-inc/greenfield/ecosystem-analysis)<a href="https://agentmods.dev/skills/prime-radiant-inc/greenfield/ecosystem-analysis"><img src="https://agentmods.dev/badge/skills/prime-radiant-inc/greenfield/ecosystem-analysis/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/prime-radiant-inc/greenfield/ecosystem-analysis"><img src="https://agentmods.dev/badge/skills/prime-radiant-inc/greenfield/ecosystem-analysis.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.00040 | $0.02652 |
| Opus 5 | $0.00020 | $0.01326 |
| Sonnet 5 | $0.00008 | $0.00530 |
| Haiku 4.5 | $0.00004 | $0.00265 |
Grade A, and why
ecosystem-analysis 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 10d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ecosystem Analysis
Extract behavioral specifications from third-party SDKs, client libraries, and ecosystem tooling. Every SDK that consumes the target's APIs encodes behavioral assumptions in executable logic -- the strongest form of specification.
When to Use This Mode
Use SDK/Ecosystem mode when the target product has:
- Public APIs consumed by third-party client libraries
- Official SDKs published on package registries
- Community-maintained client libraries on GitHub/GitLab
- Open-source integrations or plugins that interact with the target
This mode runs independently of all other intelligence sources. It requires no source code access, no runtime execution, and no container. It needs only network access to package registries and code hosting platforms.
Targets without a public SDK or third-party client ecosystem get no useful signal from this mode — skip it.
Source Origin
SDK analysis draws only from published artifacts — client libraries on package registries, open-source community integrations, and the examples in official documentation. Nothing in this mode reads the target's source code; all inputs are material the target's vendor has already published for third-party developers to consume.
All SDK-derived intelligence is public origin and goes to workspace/public/ecosystem/.
Agents
| Agent | Purpose | Output |
|---|---|---|
sdk-analyzer |
Discover and analyze SDK source code for behavioral assumptions | workspace/public/ecosystem/sdks/ |
integration-test-miner |
Extract test vectors from SDK test suites and fixtures | workspace/public/ecosystem/tests/ |
Run sdk-analyzer first (it produces the SDK inventory), then integration-test-miner (it uses the inventory to find test suites).
SDK Discovery Strategy
digraph sdk_discovery {
rankdir=TB;
"Start SDK discovery" [shape=doublecircle];
"Search target docs for SDK links" [shape=box];
"Search package registries" [shape=box];
"Search GitHub/GitLab for client libraries" [shape=box];
"Classify each SDK: official vs community" [shape=box];
"Is it a wrapper SDK?" [shape=diamond];
"Is it stale (>2 years)?" [shape=diamond];
"Add to SDK inventory" [shape=box];
"Exclude from analysis" [shape=ellipse];
"Extract behavioral claims from SDK source" [shape=box];
"Mine integration tests for test vectors" [shape=box];
"Build cross-SDK consensus report" [shape=box];
"Discovery complete" [shape=doublecircle];
"Start SDK discovery" -> "Search target docs for SDK links";
"Search target docs for SDK links" -> "Search package registries";
"Search package registries" -> "Search GitHub/GitLab for client libraries";
"Search GitHub/GitLab for client libraries" -> "Classify each SDK: official vs community";
"Classify each SDK: official vs community" -> "Is it a wrapper SDK?";
"Is it a wrapper SDK?" -> "Exclude from analysis" [label="yes"];
"Is it a wrapper SDK?" -> "Is it stale (>2 years)?" [label="no"];
"Is it stale (>2 years)?" -> "Exclude from analysis" [label="yes"];
"Is it stale (>2 years)?" -> "Add to SDK inventory" [label="no"];
"Add to SDK inventory" -> "Extract behavioral claims from SDK source";
"Extract behavioral claims from SDK source" -> "Mine integration tests for test vectors";
"Mine integration tests for test vectors" -> "Build cross-SDK consensus report";
"Build cross-SDK consensus report" -> "Discovery complete";
}
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.
- 10d ago First seen · 237 lines · 40 tokens per session scan A 1eaece7c427c
ecosystem-analysis is a skill published in the GitHub repository prime-radiant-inc/greenfield (275 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 2,652 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.
Other skills, from other repositories
benchmark
Local-only regression / benchmark skill for ui-clone-skills maintainers. Drives the standard ui-reverse-engineering pipeline against the canonical reference site (https://realfood.gov) and records AE/SSIM, iteration count, gate fail counts, and outcome to benchmark/history.csv so prompt / sub-doc / model-version drift…
ui-capture
Capture baseline evidence from a live website URL: screenshots, scroll states, hover/click behavior, parallax, timers, and transition recordings. Use when reference artifacts are needed before implementation or comparison; not to build or diagnose a clone.
write-test-plans
Interactive workflow for writing new Speky test plans for requirements lacking coverage, guided by the Speky MCP server.
speky-workflow
Guidelines for working with Speky requirements and tests via the speky MCP server tools.
SPI Flash Dump via OpenOCD
This skill should be used when the user asks to "dump SPI flash", "read EEPROM through OpenOCD", "dump flash via MCU", "read SPI through debug interface", "extract firmware from SPI", or mentions scenarios involving SPI flash connected to a microcontroller with SWD/JTAG debug access. Provides comprehensive guidance…
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…