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 yuusakuri/agent-skills --skill competitive-battlecardgit clone --depth 1 https://github.com/yuusakuri/agent-skillsWrote 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/yuusakuri/agent-skills/competitive-battlecard)<a href="https://agentmods.dev/skills/yuusakuri/agent-skills/competitive-battlecard"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/competitive-battlecard/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/yuusakuri/agent-skills/competitive-battlecard"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/competitive-battlecard.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.00052 | $0.00683 |
| Opus 5 | $0.00026 | $0.00342 |
| Sonnet 5 | $0.00010 | $0.00137 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
competitive-battlecard 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 11d 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
100% identical to competitive-battlecard — 0 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Battlecard
Create a concise, sales-ready battlecard for use against a specific competitor.
Context
You are creating a competitive battlecard for $ARGUMENTS.
Use web search to research the competitor's current product, pricing, positioning, and recent changes. If the user provides files (feature lists, win/loss data, sales call notes), read them first.
Instructions
-
Research the competitor (use web search):
- Current product offerings and features
- Pricing tiers and model
- Target market and positioning
- Recent product launches or changes
- Known strengths and weaknesses
- Customer reviews and sentiment (G2, Capterra, Reddit)
-
Create the battlecard with these sections:
Company Overview
- Founded, HQ, funding/revenue (if public)
- Target market and ICP
- Positioning in one sentence
Quick Comparison
Capability Us Them Winner [Feature area 1] [Our approach] [Their approach] [Us/Them/Tie] [Feature area 2] ... ... ... Pricing ... ... ... Support ... ... ... Where We Win
- [Advantage 1]: [Proof point or customer quote]
- [Advantage 2]: [Specific capability they lack]
- [Advantage 3]: [Better approach with reasoning]
Where They Win
- [Their strength 1]: [Our counter-positioning]
- [Their strength 2]: [How we mitigate this gap]
Common Objections & Responses
Prospect Says Respond With "Competitor X has [feature]" "[Our alternative approach and why it's better for them]" "They're cheaper" "[Value framing: total cost of ownership, ROI, hidden costs]" "They're more established" "[Our advantages: speed, innovation, focus, support]" Landmines to Plant
Questions to ask the prospect that highlight competitor weaknesses:
- "How important is [area where we excel] to your team?"
- "Have you evaluated [specific capability they lack]?"
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.
- 11d ago First seen · 78 lines · 52 tokens per session scan A 89a82a58675d
competitive-battlecard is a skill published in the GitHub repository yuusakuri/agent-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 52 tokens to every session and 683 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to competitive-battlecard, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…