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/track-campaigns/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/track-campaigns)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/track-campaigns"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/track-campaigns/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/track-campaigns"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/track-campaigns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 32 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 33 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00102 | $0.00488 |
| Opus 5.5 | $0.00041 | $0.00195 |
| Sonnet 5.5 | $0.00020 | $0.00098 |
| Haiku 4.5 | $0.00010 | $0.00049 |
Grade A, and why
track-campaigns 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.
What it actually says
Track Campaigns
I'll wrap campaign:track. Run the polling cycle, advance any sequence steps that are due, and surface the per-campaign status delta.
When This Skill Applies
- "track campaigns"
- "advance the sequences"
- "check campaign progress"
- "poll for replies"
- "sync campaign status to Notion"
NOT this skill (use launch-linkedin-campaign instead):
- "launch a campaign" — that's the create+stage flow.
NOT this skill (use answer-linkedin-comments instead):
- "reply to LinkedIn comments" — that's per-thread engagement, not campaign-level tracking.
Workflow
Step 0 — No input needed (or ask for --campaign-id <id> if user wants a single campaign)
Step 1 — Shell out
cd ~/Desktop/gtm-os && set -a && source .env.local && set +a && \
npx tsx src/cli/index.ts campaign:track
Optional: --campaign-id <id> to scope to one campaign.
Step 2 — Parse output
CLI emits per-campaign status delta: messages sent, replies detected, sequence steps advanced, errors.
Step 3 — Render
Step 4 — Offer follow-ups
"Want me to (a) personalize follow-ups for hot replies via
personalize-message, (b) generate the weekly campaign report viacampaign:report?"
Notes
- Best run on cron: every 15 min during business hours.
- Replies appear in Notion within ~2 min of posting (Unipile webhook latency).
- The CLI is idempotent — running it twice in quick succession is safe (advances nothing if no time has elapsed).
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.
- 1mo ago First seen · 53 lines · 102 tokens per session scan A da6bd93b2b15
track-campaigns is a skill published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (323 stars, last pushed 2mo ago), licensed MIT. It adds 102 tokens to every session and 488 once invoked, about $0.0004 per session on Opus 5.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-09-03.
Other skills, from other repositories
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.
deepline-org-chart
Build an interactive account org chart, leadership map, buying committee, or manager/report neighborhood around a person. Use for decision makers, reporting-line candidates, stakeholder mapping, and warm intro paths. Skip standalone email lookup and unrelated cross-company prospecting.
luma-event-campaign
DRAFT. Use when running a Luma-centered GTM event campaign: pull/export guests, enrich and score, draft invites and social, stage email+LI sequences paused for approval, and wire registration sync. Not installed by deepline skills.
event-ops-score-and-door
DRAFT. Score Luma/RSVP lists, approve against capacity, produce host-hit shortlists and day-of door packs. Systems framing — not a marketing CSV dump. Not installed by deepline skills.
toflow-manage-crm
Create, search, and update CRM records (people, companies, deals), manage custom attributes, categories, and deal pipelines. Use this whenever the user wants to look up, add, or edit CRM data, or manage a deal's pipeline stage.
toflow-manage-activities
Log calls, create follow-up tasks, and attach notes to CRM records (people, companies, deals). Use this whenever the user wants to record a call outcome, set a reminder/to-do, or capture context about a contact or account.