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 travisjneuman/.claude --skill battle-card-buildergit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/battle-card-builder)<a href="https://agentmods.dev/skills/travisjneuman/.claude/battle-card-builder"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/battle-card-builder/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/travisjneuman/.claude/battle-card-builder"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/battle-card-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 360 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00040 | $0.02548 |
| Opus 5 | $0.00020 | $0.01274 |
| Sonnet 5 | $0.00008 | $0.00510 |
| Haiku 4.5 | $0.00004 | $0.00255 |
Grade A, and why
battle-card-builder 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 9d 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Battle Card Builder
Structured frameworks for creating competitive battle cards that help sales teams win against specific competitors.
Battle Card Structure
Standard Battle Card Sections
BATTLE CARD LAYOUT:
1. COMPETITOR SNAPSHOT (top of page)
- Company name, logo, tagline
- Founded, HQ, headcount, funding/revenue
- Target market and primary use case
- Threat level: HIGH / MEDIUM / LOW
2. QUICK COMPARISON TABLE
- Feature-by-feature comparison
- Pricing comparison
- Target customer comparison
3. OUR STRENGTHS (vs. this competitor)
- 3-5 key advantages with proof points
- Customer quotes that validate each strength
4. THEIR STRENGTHS (honest assessment)
- 2-3 areas where competitor excels
- How to acknowledge without conceding
5. OBJECTION HANDLING
- Top 5-7 objections prospects raise
- Recommended responses for each
6. WIN THEMES
- 3-4 messaging themes that resonate
- Discovery questions to surface our advantages
7. LANDMINES
- Questions to plant that expose competitor weaknesses
- Features to demo that highlight differentiation
8. RECENT INTEL
- Latest product releases or changes
- Pricing changes
- Key wins/losses
- Last updated date
Competitive Intelligence Gathering
Intelligence Sources
| Source | Data Type | Refresh Frequency | Reliability |
|---|---|---|---|
| Competitor website | Pricing, features, messaging | Monthly | High |
| G2/Capterra reviews | User sentiment, complaints | Monthly | Medium-High |
| Job postings | Strategic direction, tech stack | Quarterly | Medium |
| SEC filings / investor decks | Revenue, strategy, risks | Quarterly | High |
| Patent filings | Future product direction | Quarterly | Medium |
| Win/loss interviews | Real buyer reasoning | Ongoing | High |
| Sales call recordings | Objections, competitor mentions | Ongoing | High |
| Industry analyst reports | Market positioning | Annually | High |
| Social media / forums | Product issues, sentiment | Weekly | Low-Medium |
| Conference presentations | Roadmap, vision | As available | Medium |
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.
- 9d ago First seen · 362 lines · 40 tokens per session scan A 678d0e2689a9
battle-card-builder is a skill published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 7d ago), licensed MIT. It adds 40 tokens to every session and 2,548 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-09-03.
Other skills, from other repositories
plan-review-architecture
Architecture-dimension reviewer for written plans. Use when running plan-review or directly when an architectural review is wanted. Activate for keywords like "architecture review", "data flow", "failure modes", "rollback", "edge cases", "test matrix". Scores 5 sub-dimensions 0-10, produces ranked fixes. Always cite…
plan-review-experience
Experience-dimension reviewer for written plans (UX + DX). Use when running plan-review or directly when an experience review is wanted. Activate for keywords like "UX review", "DX review", "experience review", "error states", "API ergonomics", "developer experience", "user states". Scores 5 sub-dimensions 0-10…
audit-dependencies
Use when investigating dependency bloat, security advisories, supply-chain risk, upgrade planning, or before adding a new third-party package. Activate for keywords like "deps", "dependencies", "package.json", "requirements.txt", "Cargo.toml", "audit", "CVE", "stale package", "do we use", "what depends on"…
code-review-loop
Use when opening a PR for review or when receiving review feedback. Activate for keywords like "code review", "PR review", "request review", "review feedback", "address comments", "reviewer said". Covers both ends of the loop: preparing a reviewable PR and acting on feedback rigorously. Always engage with every…
evidence-driven-debugging
Use during active debugging when you have a hypothesis to test or need to instrument a running system. Activate for keywords like "debug", "instrument", "log", "trace", "breakpoint", "what's happening at runtime", "production behavior". Pair to investigate-root-cause for the doing-it phase. Always record what you…
incremental-shipping
Use when implementing a non-trivial feature, migration, or refactor that would otherwise be a single large change. Activate for keywords like "feature flag", "incremental", "vertical slice", "migration", "rollout", "behind a flag", "ship small". Enforces vertical slicing, feature-flagged rollout, and refactor-with…