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 event4u-app/agent-config --skill competitive-moat-analysisgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/competitive-moat-analysis)<a href="https://agentmods.dev/skills/event4u-app/agent-config/competitive-moat-analysis"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/competitive-moat-analysis.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.1 | $0.00047 | $0.02411 |
| Opus 5 | $0.00023 | $0.01205 |
| Sonnet 5 | $0.00009 | $0.00482 |
| Haiku 4.5 | $0.00005 | $0.00241 |
Grade A, and why
competitive-moat-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 8d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
competitive-moat-analysis
When to use
- A strategist needs a competitor map for a market / segment — not a feature-comparison sheet, but a where-they-are-strong / where-we-are-strong / where-no-one-is read.
- A board pack or fundraise narrative claims a moat; the question is which moat, how durable, and what would erode it.
- A market-entry decision needs white-space identification — where can we win cleanly because incumbents structurally can't follow?
Do NOT use for narrative / messaging surface (route to Wing-3 positioning-strategy for the outward-facing pitch; this skill produces the internal cognition that pitch rests on), per-package adoption comparisons (route to competitive-positioning (Wing-1 package-peer comparison)), or build-vs-buy decisions (route to build-buy-partner (P1)).
Cognition cluster
- Mental model 18 — Where to play, where not to play. A moat is read as much from what we refuse to do as from what we do. Trying to win everywhere = winning nowhere. See
mental-models.md§ 18. - Mental model 28 — Inversion. "What would force a customer to leave us for an incumbent?" The inversion answer surfaces the load-bearing moat assumption. If the answer is "nothing", the moat is wishful; if the answer is concrete, that's the real fragility. See
mental-models.md§ 28. - Mental model 21 — Second-order thinking. Moats compound or decay; "feature parity today" says nothing about "feature parity in 18 months". Read each moat by its compounding rate, not its current state. See
mental-models.md§ 21. - Context-spine — customer-segment + product + org-stage. Read customer-segment for which incumbent matters in which segment (the enterprise incumbent is rarely the SMB incumbent). Read product for which moats are real vs roadmap. Read org-stage for moat realism (pre-revenue moats are claims; growth-stage moats are evidence).
Procedure
Step 0: Frame the competitive set honestly
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.
- 8d ago First seen · 160 lines · 47 tokens per session scan A 3d25048b0701
competitive-moat-analysis is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,411 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-31.
Other skills, from other repositories
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
meta-theory
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
same-set-reusable-flow-for-project-file-inventor
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
starreel-drama-production
Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the entry-point decision table (which channel each kind of customer material…
seedance-20
Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.