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 agentmods add skills/agent-engineer-master/skill-engineer/map-competitive-arenanpx skills add Agent-Engineer-Master/skill-engineer --skill map-competitive-arenagit clone --depth 1 https://github.com/Agent-Engineer-Master/skill-engineerWrote 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/agent-engineer-master/skill-engineer/map-competitive-arena)<a href="https://agentmods.dev/skills/agent-engineer-master/skill-engineer/map-competitive-arena"><img src="https://agentmods.dev/badge/skills/agent-engineer-master/skill-engineer/map-competitive-arena.svg" alt="Measured on agentmods" 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 | $0.00222 | $0.02429 |
| Opus 5 | $0.00111 | $0.01215 |
| Sonnet 5 | $0.00044 | $0.00486 |
| Haiku 4.5 | $0.00022 | $0.00243 |
Grade C, and why
map-competitive-arena scanned grade C with 1 finding 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 4d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Built with Agent Engineer Master — get your own production-ready skill: www.agentengineermaster.com/skill-engineer --> How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Map Competitive Arena
For a defined industry, produce a strategic-group map (Porter) overlaid with the McKinsey Arenas-of-Competition framing where applicable. Output: competitive-arena.md that names the actual competitive clusters within the industry, what makes leaders in each cluster win, and what prevents firms from moving between clusters.
The discipline: firms within one industry rarely compete uniformly. They form clusters that share strategic posture (scope, channel, asset model) and compete primarily within-cluster. Strategic-group analysis surfaces that structure. McKinsey's arenas framing adds dynamism — in high-growth, high-dispersion markets the group structure shifts, mobility barriers erode, and winner archetypes multiply.
Iron rules:
- Every evidence claim carries a V/C/A/I tag — see
../_shared/provenance-tagging.md. - ≥3 strategic groups identified. Single- or two-group analysis is almost always a failure of discrimination — see
references/strategic-groups.md. - 2-axis visualization mandatory (markdown table or coordinate notation). Axes must be uncorrelated, discriminating, and strategic-choice variables (not outcomes like share or profitability).
- Each group has a named basis of competition (the variable on which leaders win — e.g., scale, brand, channel access, data depth).
- Each group has a named winner archetype OR explicit statement "no clear winner archetype emerging" with reason — see
references/winner-archetypes.md. - Mobility barriers assessed per adjacent-group pair (≥1 named barrier per pair) — see
references/mobility-barriers.md. - If the upstream
size-marketarenas screen classified the market as Arena / Pre-arena / Contested mature, run the arenas overlay — seereferences/arenas-overlay.md.
Process
1. Intake — lock the frame
Confirm: industry slug, geographic scope, focal value-chain layer (same convention as map-five-forces), and whether the upstream size-market output is available. If working/market-sizing.md exists in the same industry folder, read it and extract the arenas classification. Standalone mode: ask whether the market should be treated as Arena / Pre-arena / Mature / Contested mature / Declining (defaults to Mature if unknown).
What ships with it
9 files 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.
- assets/strategic-group-template.md 5.2 KB
- evals/evals.json 3.3 KB
- references/arenas-overlay.md 5.1 KB
- references/edge-cases.md 3.0 KB
- references/learnings.md 1.2 KB
- references/mobility-barriers.md 5.1 KB
- references/strategic-groups.md 5.0 KB
- references/winner-archetypes.md 5.8 KB
- scripts/validate_arena.py 7.9 KB runs code
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.
- 4d ago First seen · 116 lines · 222 tokens per session scan C 7c6f4f579aeb
map-competitive-arena is a skill published in the GitHub repository Agent-Engineer-Master/skill-engineer (8 stars, last pushed 1mo ago), licensed MIT. It adds 222 tokens to every session and 2,429 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
extract
Run the full Semantica semantic extraction pipeline on a file or selected text — NER, relations, events, coreference resolution, triplets, and validation. Clears result cache before each run. Returns Markdown tables with entity/relation/event/triplet results and inline validator warnings.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
kayba-stage-7-fixer
Implement the approved fixes from the action plan and log all changes. Trigger when the user says "run stage 7", "implement fixes", "apply action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md to exist.