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 Ad-Superpowers/ad-superpowers-plugin --skill linkedin-performance-troubleshootergit clone --depth 1 https://github.com/Ad-Superpowers/ad-superpowers-pluginWrote 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/ad-superpowers/ad-superpowers-plugin/linkedin-performance-troubleshooter)<a href="https://agentmods.dev/skills/ad-superpowers/ad-superpowers-plugin/linkedin-performance-troubleshooter"><img src="https://agentmods.dev/badge/skills/ad-superpowers/ad-superpowers-plugin/linkedin-performance-troubleshooter/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/ad-superpowers/ad-superpowers-plugin/linkedin-performance-troubleshooter"><img src="https://agentmods.dev/badge/skills/ad-superpowers/ad-superpowers-plugin/linkedin-performance-troubleshooter.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.00109 | $0.03524 |
| Opus 5.5 | $0.00044 | $0.01410 |
| Sonnet 5.5 | $0.00022 | $0.00705 |
| Haiku 4.5 | $0.00011 | $0.00352 |
Grade A, and why
linkedin-performance-troubleshooter 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.
How it starts
The opening of the file, as written. The whole thing — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Ads Performance Troubleshooter
Purpose
Diagnose and fix common LinkedIn Ads performance problems. LinkedIn has the highest CPC ($3-8+) and CPL ($60-150) of any major ad platform, requiring specialized troubleshooting because generic advice doesn't work for LinkedIn's unique auction dynamics and B2B audience.
When to Use This Skill
Invoke when user mentions:
- High costs: "Why is my LinkedIn CPL so high?"
- Delivery issues: "My LinkedIn ads aren't spending/delivering"
- Low engagement: "Engagement is low despite high impressions"
- Cost reduction: "How do I reduce my LinkedIn ad costs?"
- Performance drops: "Why did my LinkedIn performance suddenly drop?"
Quick Diagnostic Framework
┌─────────────────────────────────────────────────────────────────────────────┐
│ LINKEDIN ADS TROUBLESHOOTING │
│ START HERE │
└─────────────────────────────────────────────────────────────────────────────┘
│
▼
What's the main problem?
│
┌───────────────────────────┼───────────────────────────┐
│ │ │
▼ ▼ ▼
HIGH CPL LOW DELIVERY LOW ENGAGEMENT
(Cost per lead (Spending <50% (CTR <0.4%)
above benchmark) of budget) │
│ │ │
▼ ▼ ▼
Go to SECTION A Go to SECTION B Go to SECTION C
Section A: High CPL Troubleshooting
Diagnostic Checklist
┌─────────────────────────────────────────────────────────────────────────────┐
│ HIGH CPL DIAGNOSIS │
└─────────────────────────────────────────────────────────────────────────────┘
│
▼
Check 1: AUDIENCE SIZE
│
┌───────────────────────┴───────────────────────────┐
│ │
▼ ▼
AUDIENCE < 50,000 AUDIENCE > 50,000
───────────────── ─────────────────
│ │
▼ ▼
Too narrow! Check 2: BID STRATEGY
Action: Remove 1-2 filters │
Impact: -20-40% CPL typically ┌───────────────┴───────────────┐
│ │
▼ ▼
MANUAL BIDDING AUTOMATED BIDDING
│ │
▼ ▼
Likely too low Check 3: FORM vs LP
Action: Switch to │
automated or increase cap ┌───────┴───────┐
▼ ▼
USING FORMS USING LP
│ │
▼ ▼
Check 4: CREATIVE Higher CPL
FATIGUE expected
(CTR declining?) (better quality)
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 · 441 lines · 109 tokens per session scan A 6e5457493c40
linkedin-performance-troubleshooter is a skill published in the GitHub repository Ad-Superpowers/ad-superpowers-plugin (5 stars, last pushed 29d ago), licensed MIT. It adds 109 tokens to every session and 3,524 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-11.
Other skills, from other repositories
traffic-diagnosis
Systematically diagnose why traffic changed — spike, drop, or shift in mix. Follow these steps in order. Each step narrows the hypothesis.
incident-postmortem
Close the learning loop after a rescue or incident — reconstruct the timeline from actionlog, run root-cause analysis (platform / site / measurement / external), produce a structured postmortem document, distill reusable insights via /learn, and propose preventive guardrails. Use after a /rescue, a CPA spike, a…
ai-hive-a2a-cancel-handoff-check
A verification workflow for tasks handed from one AI agent to another using A2A, a protocol for agent-to-agent communication. It checks remote status, task identifiers, handoff outputs, and cancellation results.
ai-hive-agents-api-session-recovery
A design guide for recovering long-running hosted-agent sessions, their execution events, and result files after interruptions.
sealeap-amazon-featured-offer-loss-triage
Triage loss of the Amazon Featured Offer by checking account health, order defect signals, price competitiveness, offer and fulfillment state, listing classification, unauthorized sellers, and external price evidence before escalating. Use when the Buy Box or purchase button disappears or repeatedly returns. Do not…
self-healing-agents
Self-Healing Agents are autonomous systems that detect their own failure modes and self-correct without human intervention.