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 charlieviettq/awesome-agent-skill --skill grad-business-ecosystemsgit clone --depth 1 https://github.com/charlieviettq/awesome-agent-skillWrote 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/charlieviettq/awesome-agent-skill/grad-business-ecosystems)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/grad-business-ecosystems"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/grad-business-ecosystems/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/charlieviettq/awesome-agent-skill/grad-business-ecosystems"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/grad-business-ecosystems.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.00103 | $0.01136 |
| Opus 5 | $0.00051 | $0.00568 |
| Sonnet 5 | $0.00021 | $0.00227 |
| Haiku 4.5 | $0.00010 | $0.00114 |
Grade A, and why
"grad-business-ecosystems" 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 9d 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.
This is a copy
95% identical to grad-business-ecosystems — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Ecosystems (Moore)
Overview
Moore's business ecosystem framework conceptualizes industries as co-evolving communities of firms, customers, and other stakeholders that collectively create and capture value. Ecosystems progress through four stages (birth, expansion, authority, renewal), and participants occupy distinct roles — keystone, dominator, or niche player — each with different strategies and implications for ecosystem health.
When to Use
- Analyzing platform-based markets or multi-firm value creation networks
- Evaluating strategic positioning within an industry ecosystem
- Assessing why an ecosystem is thriving, stagnating, or collapsing
- Planning entry strategy into an existing ecosystem or designing a new one
When NOT to Use
- When the industry is best modeled as atomistic competition (no co-evolution)
- When the analysis focuses on a single firm's internal strategy (use RBV or dynamic capabilities)
- When formal supply chain analysis with contractual specificity is needed
Assumptions
IRON LAW: Ecosystem health depends on DIVERSITY and PRODUCTIVITY — a
dominant player that extracts too much value destroys the ecosystem
it depends on.
Key assumptions:
- Firms co-evolve — strategy is shaped by and shapes the broader ecosystem
- Value is created collectively and distributed among ecosystem participants
- Ecosystem leadership requires nurturing the ecosystem, not just capturing value
- Ecosystems have life cycles — what works in birth stage fails in renewal stage
Methodology
Step 1: Define the Ecosystem Boundary
Identify the ecosystem: core value proposition, platform or focal firm, and key participant categories (suppliers, complementors, customers, competitors).
Step 2: Assess the Ecosystem Stage
| Stage | Characteristics | Key Challenge |
|---|---|---|
| Birth | Entrepreneurs define value proposition around a seed innovation | Protect ideas, build initial partnerships |
| Expansion | Scaling to broad market, attracting complementors | Achieve critical mass, fend off alternative ecosystems |
| Authority | Stable architecture, clear leader, standards established | Maintain bargaining power, encourage continued innovation |
| Renewal | Mature ecosystem faces disruption or stagnation | Reinvent or be displaced by new ecosystems |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 108 lines · 103 tokens per session scan A 86351768d2e8
"grad-business-ecosystems" is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (26 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 1,136 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to grad-business-ecosystems, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
agent-orchestrator
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
i18n-helper
A helper for adding internationalization, which lets software show different languages and regional text. It finds user-visible text written directly in code and moves it into language files.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.