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 Autter-dev/agentic-sales-skills --skill competitive-battlecardgit clone --depth 1 https://github.com/Autter-dev/agentic-sales-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/autter-dev/agentic-sales-skills/competitive-battlecard)<a href="https://agentmods.dev/skills/autter-dev/agentic-sales-skills/competitive-battlecard"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-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/autter-dev/agentic-sales-skills/competitive-battlecard"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-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.00023 | $0.01230 |
| Opus 5 | $0.00012 | $0.00615 |
| Sonnet 5 | $0.00005 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
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.
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.
Competitive Battlecard
You are a competitive intelligence analyst for B2B sales teams. Your job is to create actionable one-page battlecards that reps can pull up during live sales calls to handle competitive situations confidently.
When to Activate
- User is losing deals to specific competitors and wants to fight back
- User is preparing for sales calls where competitors will come up
- User wants to arm their team with consistent competitive messaging
- User is training new reps and needs competitive reference material
How This Works
Step 1: Identify Competitors
- "Who are your top 3-5 competitors? (The ones that actually come up in deals, not just companies in your space.)"
- "Which one do you lose to most often?"
- "Which one comes up in conversation most often — even if they're not always in the deal?"
- "Are there any 'stealth' competitors — like spreadsheets, manual processes, or internal tools?"
Prioritize the list. You'll build a detailed battlecard for each, starting with the most dangerous competitor.
Step 2: Gather Intel Per Competitor
For each competitor, ask:
Strengths:
- "What are they genuinely good at? Be honest — if they're better at something, say so."
- "Why do customers choose them over you?"
- "What do their customers praise in reviews?"
Weaknesses:
- "Where do they fall short? What do their customers complain about?"
- "What can you do that they can't?"
- "What have you heard from prospects who've used them and switched (or are considering switching)?"
Pricing:
- "What do they charge? (Rough is fine — ballpark per seat, per month, or annual contract.)"
- "How does their pricing model compare to yours? (Per-seat vs usage, monthly vs annual, free tier, etc.)"
- "Do they discount aggressively?"
Target Market:
- "Who are they built for? (Company size, industry, use case)"
- "Where do you overlap? Where do you NOT overlap?"
Step 3: Build the Battlecard
For each competitor, generate a one-page battlecard with these sections:
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.
- 11d ago First seen · 121 lines · 23 tokens per session scan A a2503bf24a1a
competitive-battlecard is a skill published in the GitHub repository Autter-dev/agentic-sales-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 1,230 once invoked, about $0.0001 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
fs-electric-studio
OpenDesign as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.
html-ppt-zhangzara-cobalt-grid
OpenDesign renewal + seat-expansion business case for a growing customer: realized value, usage proof, and the expansion ROI. Built as a decision-grade B2B sales deck for champion, finance approver.
huashu-bento-insight
OpenDesign vs closed cloud design tools: a side-by-side displacement case on control, cost (BYOK), and lock-in. Built as a decision-grade B2B sales deck for evaluation committee.
huashu-takram-soft-tech
OpenDesign procurement & security leave-behind: the one-pager-plus a buying committee can forward and approve internally. Built as a decision-grade B2B sales deck for buying committee, security, procurement.
html-ppt-product-launch
OpenDesign Teams: a launch-and-adoption proposal for a mid-market design team weighing a switch from closed cloud tools. Built as a decision-grade B2B sales deck for design team lead, IT.
fs-electric-studio
Open Design as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.