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/hoavdc/codexkit/codexkit-competitor-intelligencenpx skills add hoavdc/CodexKit --skill codexkit-competitor-intelligencegit clone --depth 1 https://github.com/hoavdc/CodexKitWhat 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 | $0.00065 | $0.01115 |
| Opus 5 | $0.00032 | $0.00558 |
| Sonnet 5 | $0.00013 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
codexkit-competitor-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 2d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Intelligence Analyst
When to Use
- When launching a new product and need to understand competitive landscape
- When sales teams need competitive battle cards
- During quarterly strategic reviews
- When a new competitor enters the market
Procedure
Step 1 — Define Intelligence Requirements
- Which competitors to profile? (direct, indirect, emerging)
- Which dimensions to analyze? (product, pricing, positioning, market share, funding)
- What decisions will this intelligence inform?
- Audience: sales, product, executive, board?
Step 2 — Competitor Profiles
For each competitor, build a profile:
- Company overview (size, funding, geography)
- Product/service offering
- Target customer and ICP
- Pricing model and known price points
- Go-to-market strategy
- Key strengths and weaknesses
- Recent moves (launches, hires, partnerships, funding)
Step 3 — Comparison Matrix
| Feature | Us | Competitor A | Competitor B | Competitor C |
|---|---|---|---|---|
| Feature 1 | ✅ | ✅ | ❌ | ✅ |
| Feature 2 | ✅ | ❌ | ✅ | ❌ |
| Pricing | $$$ | $$ | $$$$ | $ |
Step 4 — Positioning Map
Plot competitors on a 2×2 perceptual map using two key dimensions:
- X-axis: e.g., Price (Low → High)
- Y-axis: e.g., Capability (Basic → Enterprise)
Step 5 — Win/Loss Analysis
| Scenario | We Won | We Lost | Pattern |
|---|---|---|---|
| vs Competitor A | 60% | 40% | We win on features, lose on price |
| vs Competitor B | 45% | 55% | They win on brand, we win on support |
Step 6 — Counter-Strategies
For each competitor, define:
- How to position against them
- Key talking points for sales
- Features/capabilities to highlight
- Objection handling for their strengths
Inputs
| Input | Required | Format |
|---|---|---|
| Competitor list | Yes | Names and categories |
| Dimensions to track | Yes | List of comparison areas |
| Internal product data | Yes | Features, pricing, positioning |
| Win/loss data | Recommended | Deal outcomes by competitor |
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.
- 2d ago First seen · 153 lines · 65 tokens per session scan A 23a6f56ea869
codexkit-competitor-intelligence is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 1,115 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
knowledge_base
Manage the user's personal knowledge base — knowledge graph, documents, and wiki vault.
reducing-aigc-detection
Systematically reduce AIGC detection rates in academic papers (Chinese/English). Analyzes detection reports, identifies high-impact sections, applies multi-layer rewriting strategies preserving formatting/footnotes, and verifies results. Supports 维普/知网/Turnitin platforms.
defending-applications
Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…
analyzing-security
Scans code for security vulnerabilities, detects dangerous patterns, and ensures security decisions are documented. Use when running security scans, auditing code, or checking for OWASP issues, injection risks, or sensitive data leaks. Automatically triggered on new modules, security-related changes, or post-refactor.
architecting-security
安全架构与治理：威胁建模 (STRIDE/PASTA/LINDDUN)、零信任身份架构、IAM/SSO/MFA/PAM、合规框架 (SOC2/PCI/HIPAA/GDPR)、DLP、隐私工程、安全控制设计。Use when designing security architecture, threat modeling new systems, implementing zero-trust identity, designing IAM/SSO/PAM, building compliance evidence chains, or planning privacy-by-design.
building-agent-systems
AI agent and LLM system engineering reference covering single-agent dev (ReAct, tool calling, plan-execute), multi-agent coordination (swarm, role decomposition, file locking), LLM security (prompt injection, jailbreak defense, output filtering), RAG architecture (chunking, hybrid retrieval, rerank), and prompt…