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 Frontal-so/outbound-skills --skill job-changesgit clone --depth 1 https://github.com/Frontal-so/outbound-skillsWrote 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/frontal-so/outbound-skills/job-changes)<a href="https://agentmods.dev/skills/frontal-so/outbound-skills/job-changes"><img src="https://agentmods.dev/badge/skills/frontal-so/outbound-skills/job-changes/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/frontal-so/outbound-skills/job-changes"><img src="https://agentmods.dev/badge/skills/frontal-so/outbound-skills/job-changes.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.00072 | $0.00826 |
| Opus 5 | $0.00036 | $0.00413 |
| Sonnet 5 | $0.00014 | $0.00165 |
| Haiku 4.5 | $0.00007 | $0.00083 |
Grade A, and why
job-changes 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 9d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Job Change Signals
Job changes are the #2 buying signal by purchase correlation. New leaders have a mandate for early wins, vendor amnesty period, and budget air cover. Response rate is 3x higher than cold outreach, with peak engagement at days 14-45.
Reference Files
- Read
{SKILL_BASE}/resources/timing/job-change-tracking.mdfor Clay setup and tracking methods - Read
{SKILL_BASE}/resources/buying-signals.mdfor signal ranking and benchmarks
Why Job Changes Work
- 3x higher response rate vs cold outreach
- Peak engagement: days 14-45 after the change (vendor amnesty period)
- New leaders actively build their stack in first 90 days
- Trust already established with former champions
- Champion job change to target account = 75 points (Tier 1 signal)
Clay Setup - Two Methods
Method 1: Monitor Existing Table
- Go to Actions > Monitor for Job Changes
- Specify the LinkedIn URL column
- Save and run - new row created for each detected change
Method 2: Create New Tracking Table
- +Create New > Table > Track Job Changes
- Include "Person LinkedIn URL" for future monitoring
- Include "Company LinkedIn URL" to detect if they already changed
Historical vs Future
- Historical: Include both Person + Company LinkedIn URLs - checks if contact already changed
- Future: Only Person LinkedIn URL - monitors ongoing changes
Timing Framework
| Window | Multiplier | Action |
|---|---|---|
| Days 0-13 | Too early | Monitor only - they are still settling in |
| Days 14-45 | Peak (1.5x) | Immediate outreach - vendor amnesty window |
| Days 46-90 | Good (1.0x) | Standard outreach - still building stack |
| Days 90+ | Declining (0.7x) | Lower priority - stack likely set |
Outreach Template
Hey congrats on the new role at {{company}}.
As you are taking over {{department}}, curious how you are
currently handling {{relevant_problem}}?
We helped {{similar_company}} with exactly that.
Key Rules
- Do NOT mention you tracked their job change ("I saw you moved to...")
- Reference the role/department naturally, not the signal itself
- Former champions get AE-owned outreach (warm relationship)
- New contacts at target accounts get SDR sequence
- Stack with other signals for compound scoring: job change (75pts) + website visit (50pts) = Hot
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.
- 9d ago First seen · 82 lines · 72 tokens per session scan A 355006d638ee
job-changes is a skill published in the GitHub repository Frontal-so/outbound-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 826 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-31.
Other skills, from other repositories
objection-analyzer
Find out which objections your outbound gets, how well your team handled them, and what to say next time. Use whenever the user wants to analyze the objections in their replies, rank the most frequent ones, know how to handle a specific objection, coach reps on their objection answers, build an objection playbook or…
audience-icp-filter
Filter an existing audience or lead list against your ICP and split it into ready-to-sequence segments. Use when someone already has a list of people — an audience in their sales tool, a CSV or CRM export, event or webinar attendees, registrants, a Sales Navigator import, a newsletter or community export — and wants…
sales-nav-search-builder
Generate a precise LinkedIn Sales Navigator search URL from a natural-language ICP description — for sales prospecting, outbound outreach, lead generation, and B2B targeting. Use whenever the user asks for a Sales Nav URL, a LinkedIn search URL, an outbound prospecting query, a search for a persona or role, wants to…
team-performance-dashboard
Generate your Team Performance Dashboard from your La Growth Machine data: a head-of-sales cockpit that ranks each sender (rep) on reply rate, your success event (signups/meetings/deals) and conversion, surfaces hot leads going cold, and turns your best reps' campaigns into a coaching playbook for the rest. Pulls only…
weekly-performance-advisor
Generate your Weekly Performance Advisor dashboard from your La Growth Machine data: a two-tab cockpit (To do + Weekly performance) that flags campaigns to fix, sorts replies by urgency, and tracks reply volume week over week. It pulls only YOUR live LGM data, scores each running campaign against baked 3-zone…
won-deal-icp-finder
Audit your biggest closed-won deals to find your PROVEN ideal customer profile, then find more accounts like them. Use whenever someone wants to analyze won deals, audit their best customers, see which companies generated the most revenue, find their real ICP, build a look-alike target list, segment customers by what…