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/event4u-app/agent-config/competitive-positioningnpx skills add event4u-app/agent-config --skill competitive-positioninggit 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-positioning)<a href="https://agentmods.dev/skills/event4u-app/agent-config/competitive-positioning"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/competitive-positioning.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.01535 |
| Opus 5 | $0.00023 | $0.00767 |
| Sonnet 5 | $0.00009 | $0.00307 |
| Haiku 4.5 | $0.00005 | $0.00153 |
Grade A, and why
competitive-positioning 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
competitive-positioning
When to use
- A peer / reference / competitor repository was named and the team needs a structured comparison, not a vibes summary.
- A pattern from another package is being considered for adoption and the trade-off needs to land in writing.
- Positioning prose for a README / launch / pricing page needs an ours-vs-theirs decisions table to anchor on.
Do NOT use for general repo audits (route to analyze-reference-repo),
upstream-contribution decisions (route to upstream-contribute), or
DCF-style valuation work (route to dcf-modeling).
Cognition cluster
- Mental model 1 — First principles. Strip the comparison to the
outcome each package promises its user, not the feature lists. Two
packages with overlapping features can promise different outcomes
and therefore are not direct competitors. See
docs/contracts/mental-models.md§ 1. - Mental model 24 — Optionality. A pattern that costs little to
adopt and preserves exit value beats a "better" pattern that locks
the package in. Score adoption cost AND exit cost on every row. See
mental-models.md§ 24. - Mental model 12 — Inversion. For each axis, ask "what would
we do if we wanted to lose on this axis?" The answer surfaces the
invariants the comparison must preserve. See
mental-models.md§ 12. - Product context-spine slot. Read the product slot for
segment / focal job / non-goals before picking axes; the comparison
is only legitimate inside our own scope. See
context-spine.
Procedure
1. Frame the comparison
Name the peer in one sentence: "Package P promises outcome O for segment S." If you cannot, the peer is not a peer; abort.
2. Pick the axes
3–7 axes, derived from the product spine slot, never from the peer's marketing site. Each axis must:
- Be observable from the artefacts (repo, docs, package output).
- Map to a real user outcome, not a feature checklist.
- Be able to separate the two packages on at least the threshold of "matters to a switch decision".
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 · 162 lines · 47 tokens per session scan A af5bbfdf648c
competitive-positioning 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 1,535 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.