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 First-Touch-Inc/firsttouch-agent-skill-packs --skill campaign-pause-and-fixgit clone --depth 1 https://github.com/First-Touch-Inc/firsttouch-agent-skill-packsWrote 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/first-touch-inc/firsttouch-agent-skill-packs/campaign-pause-and-fix)<a href="https://agentmods.dev/skills/first-touch-inc/firsttouch-agent-skill-packs/campaign-pause-and-fix"><img src="https://agentmods.dev/badge/skills/first-touch-inc/firsttouch-agent-skill-packs/campaign-pause-and-fix/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/first-touch-inc/firsttouch-agent-skill-packs/campaign-pause-and-fix"><img src="https://agentmods.dev/badge/skills/first-touch-inc/firsttouch-agent-skill-packs/campaign-pause-and-fix.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.00090 | $0.01629 |
| Opus 5 | $0.00045 | $0.00814 |
| Sonnet 5 | $0.00018 | $0.00326 |
| Haiku 4.5 | $0.00009 | $0.00163 |
Grade A, and why
campaign-pause-and-fix 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Campaign Pause & Fix
Outcome: A running campaign stops cleanly, the problem gets fixed, and the motion restarts without double-touching anyone. This is the mid-send escape hatch for every other play.
First-run onboarding gate
Before running this skill for the first time in a workspace, load ../../references/onboarding.md and complete the onboarding questions. Do not proceed until you know: LinkedIn account type (free/basic = no connection notes; recommend 10 connection requests/day and never exceed the FirstTouch max of 20/day; Sales Navigator/Premium = connection notes available; recommend 20 connection requests/day and never exceed the FirstTouch max of 30/day), HubSpot access (MCP, service key/private app token, HubSpot list only, or none), and which play the user wants to run. Recommend high-intent plays before outbound to keep the LinkedIn account healthy. If HubSpot is unavailable, do not run HubSpot-specific steps unless the user provides a HubSpot list FirstTouch can access.
When to use
- "Pause the campaign" / "stop sending right now"
- Bad copy, wrong audience, or a broken variable shipped in a live flow
- Acceptance or reply rates dropped mid-run, or replies are negative
- The user wants to change the message or audience of a flow that is already running
- The sender seat shows Action required, Disconnected, or Restricted in FirstTouch Social settings mid-campaign
Step-by-step
1. Identify the running motion
Find the flow the user means - do not guess from chat memory:
list_flow_plansto list flows; confirm the exact flow plan with the user by name.list_flow_plan_enrollments(orlist_enrollments) to see who is in it and in what state: awaiting, in-progress, completed, failed, canceled.list_linkedin_outreach_queuefor what is queued to send next.
Present a status snapshot before touching anything: total enrolled, sent so far, queued next 24h, awaiting approval.
2. Stop the bleeding
- Unpublish/pause the flow with
manage_flow_publication. This stops new sends; it does not undo anything already sent. - Confirm to the user what is now frozen and what already went out. Anything already sent is a fact to work with, not something to hide.
- If the trigger was a non-Available seat status (Action required / Disconnected / Restricted), stop sends for that seat and follow the account-statuses section in
../../references/troubleshooting.mdbefore any fix-and-restart.
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 · 90 lines · 90 tokens per session scan A 5a08187a97ee
campaign-pause-and-fix is a skill published in the GitHub repository First-Touch-Inc/firsttouch-agent-skill-packs (5 stars, last pushed 2mo ago), licensed MIT. It adds 90 tokens to every session and 1,629 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-31.
Other skills, from other repositories
linkedin-mcp
Use LinkedIn data for profile, company, job, post, feed, inbox, recruiting, and outreach work through the bundled LinkedIn MCP server. Use only for an explicit LinkedIn request.
social-carousel
A three-card social media carousel where one headline continues across three square images. The cards can include a brand mark, numbering, a visual focus, and a call to action.
linkedin-content
Use when writing the actual words of one LinkedIn feed post — turning a raw idea, story or asset into ready-to-paste copy: a text post, a document/carousel cover with slide copy and caption, or a short native-video script. Covers fixing a weak hook, reformatting a wall of text for the mobile feed, and a CTA that…
sdr-humanizer
Transform AI-generated sales messages into natural, human-like conversations that build trust and rapport.
gr-social-distill
A content-repurposing workflow that turns one published blog post into several social-media formats, including an X thread, a Xiaohongshu post, a LinkedIn carousel, and a dev.to or Zenn article.
supermemory
Semantic memory layer powered by vector search. Store, recall, and connect conversation insights across all customer interactions.