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 matellez/claude-skills --skill competitive-intelligencegit clone --depth 1 https://github.com/matellez/claude-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/matellez/claude-skills/competitive-intelligence)<a href="https://agentmods.dev/skills/matellez/claude-skills/competitive-intelligence"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/competitive-intelligence/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/matellez/claude-skills/competitive-intelligence"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/competitive-intelligence.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.00152 | $0.01035 |
| Opus 5.5 | $0.00061 | $0.00414 |
| Sonnet 5.5 | $0.00030 | $0.00207 |
| Haiku 4.5 | $0.00015 | $0.00103 |
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 1mo 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.
This is a copy
100% identical to competitive-intelligence — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Intelligence: Interview Prep Briefs
This skill runs automatically when the user is preparing for an interview or researching a specific company for a job application. Always search the web before writing anything. Do not rely on training data for company information.
HOW TO SET UP THIS SKILL
Replace the [PLACEHOLDER] sections below with your own background before adding this file to your Claude Project. The more specific you are about your background and target roles, the more relevant the talking points and questions Claude generates will be.
Who This Person Is
Name: [Your full name]
Target roles: [List 3-5 role titles you are actively applying for]
Background: [2-3 sentences summarizing your core expertise, years of experience, key tools, and functional areas.]
Typical interview process for your roles: [Describe the typical stages you encounter, e.g.:
- Recruiter screen
- Hiring manager
- Panel interview
- Take-home exercise]
Step 1: Search First
When this skill triggers, immediately run web searches on the company. Do not write the brief until you have current information from the web.
Required searches:
- Company name + "news [current year]"
- Company name + "funding" or "acquisition" or "PE"
- Company name + your functional area
- Company name + "reviews" or "Glassdoor"
- Company name + job title if provided
Run additional searches if gaps remain.
Step 2: Build the Intel Brief
Deliver the output in this exact format.
COMPANY INTEL BRIEF [Company Name] Prepared: [Today's date] Role: [Role title if provided, otherwise "Not specified"]
WHAT THEY DO [2-3 sentences. Plain language. What product or service, who they sell to, what problem they solve. No marketing speak.]
OWNERSHIP AND FINANCIAL CONTEXT [Public or private. PE-backed, VC-backed, or bootstrapped. Any recent funding rounds, acquisitions, or notable financial events. If PE-backed, name the firm if known.]
RECENT NEWS (last 6 months)
- [Item 1: what happened, source, date]
- [Item 2: what happened, source, date]
- [Item 3: what happened, source, date] [If no recent news is found, say so directly.]
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.
- 1mo ago First seen · 140 lines · 152 tokens per session scan A ef8c0d5d422f
competitive-intelligence is a skill published in the GitHub repository matellez/claude-skills (4 stars, last pushed 6mo ago), licensed MIT. It adds 152 tokens to every session and 1,035 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to competitive-intelligence, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.
rudder-instrumentation-debugging
Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.
rudder-ai-events-verify
Verifies RudderStack AI events locally: captures what an instrumented app or MCP server sends, validates it against the AI events v0.3 schema, and checks joins, counts, identity and content. Use when testing AI events, or when AI or MCP events look wrong or missing.
helius
Skill "helius" from helius-labs/core-ai, covering helius — build on solana, prerequisites, 1. helius mcp server, 2. mcp router surface and 3. api key.