Borrowing it
Nothing to install: this file belongs to Othmane-Khadri/YALC-the-GTM-operating-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Othmane-Khadri/YALC-the-GTM-operating-system/main/.claude/skills/lemlist/competitor-finder/SKILL.mdgit clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-systemWrote 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/othmane-khadri/yalc-the-gtm-operating-system/competitor-finder)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/competitor-finder"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/competitor-finder/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/othmane-khadri/yalc-the-gtm-operating-system/competitor-finder"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/competitor-finder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00107 | $0.01036 |
| Opus 5 | $0.00053 | $0.00518 |
| Sonnet 5 | $0.00021 | $0.00207 |
| Haiku 4.5 | $0.00011 | $0.00104 |
Grade A, and why
competitor-finder 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 13d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitor Finder — Map the competitive landscape
You are a competitive intelligence analyst. You identify who a company competes with, how each player is positioned, and where the differentiation opportunities are — with a specific focus on what this means for outbound messaging and objection handling.
Step 1 — Gather inputs
Ask in a single message:
- Company / product: website URL or brief description
- Known competitors (if any): to include + validate
- Context: are they trying to position against a specific competitor, or map the full landscape?
Step 2 — Identify the competitive set
Identify 3 tiers of competition:
Tier 1 — Direct competitors: Same category, same buyer, similar price point. These are the names prospects will compare you to.
Tier 2 — Indirect competitors: Different approach to the same problem. Often the "we built it in-house" or "we use a combination of cheaper tools" option.
Tier 3 — Status quo: Doing nothing, spreadsheets, manual process, or a legacy tool. Often the most common "competitor" — don't ignore it.
Sources to check: G2 "Alternatives" section, Capterra comparisons, Google "[product] vs", "[product] alternative", ProductHunt, LinkedIn job postings mentioning tool names.
Step 3 — Map each competitor
For each direct competitor (Tier 1), produce a competitor card:
[Competitor Name] Website: [URL] Category positioning: [How they describe themselves] Target ICP: [Who they primarily serve] Price point: [Approx. — signals buyer level] Key strengths: [What they do well — be honest, don't minimize] Key weaknesses: [Where they fall short — from reviews and customer feedback] Differentiating claim: [Their #1 unique selling point] Why prospects choose them: [Real reasons, not spin] Why prospects choose us instead: [Honest differentiation] Outreach angle when they're using this competitor: [Specific hook]
Step 4 — Output the competitive landscape
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.
- 13d ago First seen · 116 lines · 107 tokens per session scan A 41b6fce3d4ca
competitor-finder is a skill published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (301 stars, last pushed 23d ago), licensed MIT. It adds 107 tokens to every session and 1,036 once invoked, about $0.0005 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
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
kn-spec
Use when creating a specification document for a feature (SDD workflow).
kn-handoff
Use when a feature crosses repository boundaries and one side must hand work to the other - generates a self-contained frontend-to-backend brief or backend-to-frontend API contract.
kn-flow
Use when orchestrating a full Knowns spec or task wave through planning, implementation, review, integration, and verification, optionally using sub-agents when scopes are parallel-safe.
kn-research
Use when you need to understand existing code, find patterns, search project knowledge, investigate current external facts, or explore a large codebase before implementation.
kn-debug
Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn.