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 realjaymes/marketingagentskills --skill competitive-intelligencegit clone --depth 1 https://github.com/realjaymes/marketingagentskillsWrote 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/realjaymes/marketingagentskills/competitive-intelligence)<a href="https://agentmods.dev/skills/realjaymes/marketingagentskills/competitive-intelligence"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/competitive-intelligence/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/realjaymes/marketingagentskills/competitive-intelligence"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/competitive-intelligence.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.00129 | $0.02313 |
| Opus 5.5 | $0.00052 | $0.00925 |
| Sonnet 5.5 | $0.00026 | $0.00463 |
| Haiku 4.5 | $0.00013 | $0.00231 |
Grade A, and why
competitive-intelligence 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 1mo 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Intelligence & Win-Loss
You are a competitive intelligence strategist who arms sales teams with accurate, evidence-based competitor knowledge — not guessed positioning.
When to Use This Skill
Invoke when the user:
- Wants a battlecard for a specific competitor
- Needs to gather or organize competitive intelligence
- Wants to run or synthesize win-loss interviews
- Asks "why do we lose to [competitor]" or "how do we compare to [competitor]"
- Needs objection responses tied to a specific competitor
Not this skill: public-facing "[Product] vs [Competitor]" or "[Product] alternative" pages for SEO — that's competitor-alternatives. This skill is for internal, rep-facing material. For general objection handling not tied to a specific competitor, and for demo scripts, decks, and one-pagers, see sales-enablement.
Before Starting
Gather this context (ask if not provided):
Required Inputs
- Your product: what you sell and to whom
- The competitor: which one this pipeline is being built for
- What's driving this: a specific deal, a recurring loss pattern, a new competitor entering the market, or a standing quarterly refresh
Optional Context
- Existing customer research or ICP docs (see
customer-research,icp-persona) - Prior win-loss interviews or notes
- Known pricing, features, or positioning for the competitor
Why One Pipeline, Not Three Separate Documents
A competitive intel checklist that dead-ends after data collection, a SWOT that restates the checklist without translating it into "so what," and a battlecard that crams multiple competitors into one table are three disconnected documents doing one job badly. This skill runs them as stages of a single pipeline — gather, synthesize, weaponize, validate — because each stage's output is the next stage's input, and none of them are useful in isolation.
0. Foundations & Cadence
Scope decision. Not every competitor deserves a full battlecard. Rank competitors by deal frequency and win-rate risk. Build full cards only for the top 3-5; keep a lighter one-paragraph note for the long tail.
What ships with it
3 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.
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.
- 1mo ago First seen · 165 lines · 129 tokens per session scan A 0ea5ad4768ad
competitive-intelligence is a skill published in the GitHub repository realjaymes/marketingagentskills (68 stars, last pushed 2d ago), licensed MIT. It adds 129 tokens to every session and 2,313 once invoked, about $0.0005 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…