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 tahirraufkeeyu/software-development-agent-stack--sdas --skill competitive-analysisgit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/competitive-analysis)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/competitive-analysis"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/competitive-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.00053 | $0.01673 |
| Opus 5 | $0.00026 | $0.00837 |
| Sonnet 5 | $0.00011 | $0.00335 |
| Haiku 4.5 | $0.00005 | $0.00167 |
Grade A, and why
competitive-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 7d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Trigger this skill when:
- A rep enters a deal where a specific competitor is incumbent or finalist (e.g. "they're also evaluating Gong").
- A CRO or PMM is refreshing the quarterly battlecard library.
- A new competitor enters the category and the field team needs positioning quickly.
- A deal is stalling and the rep suspects the competitor is winning on a specific angle.
Do not use this for market-level category analysis. This skill is adversarial and per-competitor. For a category landscape, use a market research tool.
Inputs
Required:
competitor_name— e.g. "Gong", "Outreach", "Clari".our_product_context— a sentence describing our product and category so the output contrasts meaningfully.
Optional:
deal_context— the specific deal this battlecard is for (vertical, size, persona). Tightens the output.known_objections— objections the rep has already heard in this deal.internal_win_loss_notes— paste from CRM or Gong.
Outputs
A single Markdown battlecard with these sections:
- Header — competitor name, category, one-sentence positioning in their words.
- Target ICP — who they sell to best.
- Pricing — public list prices if available, leaked/anecdotal if not, with source attribution.
- Strengths — 3-5 bullets where they genuinely outperform us.
- Weaknesses — 3-5 bullets, each backed by a review citation or public incident.
- Differentiators (ours vs. theirs) — side-by-side, no puffery.
- Objection handling — 3-5 common objections raised in deals against them, with recommended response patterns.
- Landmines — questions we can ask in discovery that expose their weakness.
- Win/loss patterns — when we tend to win, when we tend to lose.
- Proof points — case studies, G2 stats, security certs to cite.
See references/battlecard-template.md for the full template.
Tool dependencies
- WebSearch / WebFetch — required. Need to pull competitor website, pricing pages, G2 and Capterra reviews, and recent news.
- Salesforce or HubSpot MCP — optional; pulls win/loss notes on deals tagged with this competitor.
- Notion MCP — optional; read the existing battlecard archive if one exists.
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.
- 7d ago First seen · 121 lines · 53 tokens per session scan A 30ee04025898
competitive-analysis is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 1,673 once invoked, about $0.0003 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-30.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…