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/campaign-dashboard/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/campaign-dashboard)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/campaign-dashboard"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/campaign-dashboard/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/campaign-dashboard"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/campaign-dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium MCP Rug Pull · line 42 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]
- medium MCP Rug Pull · line 53 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.00078 | $0.00707 |
| Opus 5 | $0.00039 | $0.00353 |
| Sonnet 5 | $0.00016 | $0.00141 |
| Haiku 4.5 | $0.00008 | $0.00071 |
Grade A, and why
campaign-dashboard 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Campaign Dashboard Skill
Opens the GTM-OS campaign visualization dashboard in the browser — Heyreach/Lemlist-style cards grid with per-lead timelines and variant comparison.
When This Skill Applies
- "campaign status" / "campaign dashboard"
- "show me campaigns" / "visualize campaigns"
- "what's the state of campaigns"
- "open campaign view" / "campaign pipeline"
- "show me the leads for [campaign name]"
- "how are outreach campaigns doing" (when visual context is implied)
NOT this skill (use campaign-intelligence instead):
- "campaign report" / "weekly campaign report" → generates a Notion text report
- "compare variants" / "which angle is winning" → text analysis
What This Skill Does
- Starts the GTM-OS server (if not already running)
- Opens the campaign dashboard at
http://localhost:3847/campaigns - Shows campaign cards with live metrics from SQLite
- Drill into any campaign for per-lead timeline + variant A/B comparison
What This Skill Does NOT
- Generate Notion reports (that's campaign-intelligence)
- Modify campaigns, leads, or variants
- Send any LinkedIn messages
Workflow
Step 1: Start the GTM-OS Dashboard
npx tsx src/cli/index.ts campaign:dashboard
This starts the Hono.js server on port 3847 and opens /campaigns in the browser.
Step 2: If User Wants a Specific Campaign
If the user mentioned a specific campaign name:
- Query the campaign ID:
npx tsx -e "
import { db } from './src/lib/db/index.ts';
import { campaigns } from './src/lib/db/schema.ts';
const rows = await db.select({ id: campaigns.id, title: campaigns.title }).from(campaigns);
console.log(JSON.stringify(rows, null, 2));
"
- Open the specific campaign detail page:
open "http://localhost:3847/campaigns/{campaignId}"
Step 3: Report Back
After opening the dashboard, tell the user:
- The URL that was opened
- A quick summary of what they'll see (number of campaigns, active count, total leads)
- Remind them they can filter by status and search leads in the UI
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 · 88 lines · 78 tokens per session scan A 8467cf484e35
campaign-dashboard 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 78 tokens to every session and 707 once invoked, about $0.0004 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.