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 agentmods add skills/taizen-ai/taizen-claude-plugins/competitive-intelligencenpx skills add taizen-ai/taizen-claude-plugins --skill competitive-intelligencegit clone --depth 1 https://github.com/taizen-ai/taizen-claude-pluginsWrote 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/taizen-ai/taizen-claude-plugins/competitive-intelligence)<a href="https://agentmods.dev/skills/taizen-ai/taizen-claude-plugins/competitive-intelligence"><img src="https://agentmods.dev/badge/skills/taizen-ai/taizen-claude-plugins/competitive-intelligence.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.00031 | $0.03195 |
| Opus 5 | $0.00015 | $0.01597 |
| Sonnet 5 | $0.00006 | $0.00639 |
| Haiku 4.5 | $0.00003 | $0.00319 |
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 6d 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 — 461 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Intelligence Skill
Comprehensive competitive analysis and sales enablement materials.
Purpose
Equip teams with actionable competitive intelligence to win more deals and create compelling differentiation.
Required Integrations
Connect these data sources to enable full functionality. Claude will prompt you to connect any missing integrations.
Data Sources
# COMPETITIVE DATA SOURCES
# Uncomment and configure the sources you want to use
# Enterprise Search (searches across all internal sources)
- source: enterprise_search
connector: "{{GLEAN | MOVEWORKS | ELASTIC}}"
data:
- internal_docs
- wiki_content
- shared_drives
- slack_history
- email_archives
# Review & Comparison Sites
- source: g2
enabled: true
- source: capterra
enabled: true
- source: trustradius
enabled: true
- source: gartner_peer_insights
enabled: false
# Market Intelligence
- source: crunchbase
enabled: true
- source: pitchbook
enabled: false
- source: owler
enabled: true
# Web & Content
- source: competitor_websites
urls:
- "{{COMPETITOR_1_URL}}"
- "{{COMPETITOR_2_URL}}"
- "{{COMPETITOR_3_URL}}"
- source: web_search
enabled: true
# Social & Community
- source: linkedin
enabled: true
- source: twitter
enabled: true
- source: reddit
subreddits:
- "{{RELEVANT_SUBREDDIT_1}}"
- "{{RELEVANT_SUBREDDIT_2}}"
# Internal Sources
- source: internal_docs
connector: "{{GOOGLE_DRIVE | SHAREPOINT | NOTION | CONFLUENCE}}"
paths:
- "/Competitive Intel/"
- "/Sales Enablement/Battlecards/"
- source: crm
connector: "{{SALESFORCE | HUBSPOT}}"
data:
- win_loss_notes
- competitive_mentions
- deal_outcomes_by_competitor
- source: call_recordings
connector: "{{GONG | CHORUS | CLARI}}"
data:
- competitive_mentions
- objection_patterns
- win_loss_call_analysis
# News & SEC Filings
- source: sec_filings
enabled: true
- source: news_feeds
enabled: true
Your Competitor List
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.
- 6d ago First seen · 461 lines · 31 tokens per session scan A 8c5abed5c82b
competitive-intelligence is a skill published in the GitHub repository taizen-ai/taizen-claude-plugins (8 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 3,195 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-08-31.
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…
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…
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…