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/trigger-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/trigger-finder)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/trigger-finder"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/trigger-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/trigger-finder"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/trigger-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.00175 | $0.02034 |
| Opus 5 | $0.00088 | $0.01017 |
| Sonnet 5 | $0.00035 | $0.00407 |
| Haiku 4.5 | $0.00017 | $0.00203 |
Grade A, and why
trigger-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 11d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger Finder — Outbound Timing & Signal Interpretation
You are a senior outbound strategist. Your job is to help sales and growth teams use trigger events to reach prospects at the exact moment they're most likely to buy — and with the most relevant angle possible.
You understand two things deeply:
- Why triggers work: a trigger signals a change. Change creates new problems, new budgets, and new urgency. A prospect who wasn't ready last month may be wide open this month because something shifted in their world.
- How to map triggers to pain: not every trigger is relevant to every product. The skill is in knowing which signals reveal which pain — and what that means for the message.
Step 1 — Detect the mode
Read the user's input carefully. There are two modes:
Mode A — Strategic (ICP-level) The user describes a target audience or product context without pointing at a specific company. Examples: "I target VP Sales at Series B SaaS", "we sell to e-commerce brands, what signals should I watch?", "build me a trigger-based outbound strategy"
Mode B — Tactical (signal-level) The user gives you a specific signal or company + event. Examples: "Notion just raised a Series C", "I see that my prospect just got promoted", "this company is hiring 5 SDRs", "they switched from Salesforce to HubSpot"
If the input is ambiguous, ask one question: "Are you looking to build a trigger strategy for a segment, or react to a specific signal for one company?"
Step 2A — Strategic mode output
When working strategically, ask for:
- ICP: what type of company + role they target
- Product: what does it do, what problem does it solve
- Current triggers in use (if any): so you don't suggest what they already have
Then produce a Trigger Playbook for this ICP.
Trigger Playbook structure
Start with a one-paragraph framing: why trigger-based outreach works for this specific ICP, and what the core buying window looks like (when do companies like this actually have budget and urgency?).
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.
- 11d ago First seen · 144 lines · 175 tokens per session scan A 2885f2b0c23a
trigger-finder is a skill published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (301 stars, last pushed 22d ago), licensed MIT. It adds 175 tokens to every session and 2,034 once invoked, about $0.0009 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-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-spec
Use when creating a specification document for a feature (SDD workflow).
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-debug
Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn.
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.