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 agentmods add skills/frontal-so/outbound-skills/tech-changesnpx skills add Frontal-so/outbound-skills --skill tech-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/tech-changes)<a href="https://agentmods.dev/skills/frontal-so/outbound-skills/tech-changes"><img src="https://agentmods.dev/badge/skills/frontal-so/outbound-skills/tech-changes.svg" alt="Measured on agentmods" 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 | $0.00074 | $0.00949 |
| Opus 5 | $0.00037 | $0.00475 |
| Sonnet 5 | $0.00015 | $0.00190 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
tech-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 5d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Stack Change Signals
Tech stack changes are the #4 buying signal by purchase correlation. An active change project indicates openness to new vendors, fresh pain from transition, and new gaps in workflow. This is an active buying window.
Reference Files
- Read
{SKILL_BASE}/resources/buying-signals.mdfor signal ranking (#4 by purchase correlation) - Read
{SKILL_BASE}/resources/signal-taxonomy.mdfor adjacent vendor triggers (Category III, items 1-7) and integration signals
Why Tech Changes Work
- Active buying window - they are already evaluating and switching tools
- Fresh pain from transition - migration creates new gaps
- New gaps in workflow - removed tool leaves unmet needs
- Open mindset - already committed to change, lower switching resistance
- Technology change = Tier 2 signal (35-45 points depending on relevance)
Detection Methods
BuiltWith / Wappalyzer
- Monitor target accounts for technology additions/removals
- Clay integration: Enrich company with tech stack data
- Track changes over time (tech added, tech removed)
Job Postings
- Job descriptions mentioning new tools = migration signal
- "Experience with Salesforce" when they currently use HubSpot = CRM switch
- Clay: Scrape job postings, extract tool mentions, compare to known stack
LinkedIn Activity
- Engineers/admins posting about new tool implementations
- Company page announcing new partnerships/integrations
- Trigify: Track engagement on vendor content
Integration Announcements
- New integration released (taxonomy trigger #13)
- Tech ecosystem expansion signals priorities
- Partner directories and marketplace listings
Scoring by Change Type
| Tech Change | Points | Rationale |
|---|---|---|
| Removed competitor from stack | 45 | Active replacement window |
| Added adjacent tool | 35 | Stack expansion, integration opportunity |
| Job posting mentions new tool | 30 | Migration in progress |
| Added your category competitor | 20 | Already solved, but may be unhappy later |
| General stack growth (5+ tools added) | 25 | Active buying mode |
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.
- 5d ago First seen · 95 lines · 74 tokens per session scan A 614f0e0494c9
tech-changes is a skill published in the GitHub repository Frontal-so/outbound-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 949 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
a-b-testing
Design statistically sound GTM experiments for copy, channels, landing pages, sequencing, pricing, and funnel conversion. Produces hypothesis, sample-size logic, success metrics, test plan, analysis method, and scale/stop/kill recommendation. Use when planning A/B tests, split tests, or experiment roadmaps.
attribution
Build practical B2B attribution models across first touch, lead creation, opportunity creation, multi-touch, account-based influence, and sales-sourced revenue. Produces model comparison, UTM governance, source-of-truth rules, and channel ROI view. Use when marketing and sales disagree on source or ROI.
campaign-analytics
Analyze campaign performance from deliverability through revenue: delivery, engagement, replies, meetings, SQOs, pipeline, CAC, and payback. Produces diagnostic scorecard, root-cause analysis, benchmark comparison, and next-action plan. Use when deciding whether to scale, fix, or kill campaigns.
gtm-metrics
Build a GTM metrics system for SaaS: funnel conversion, pipeline velocity, win rates, CAC, payback, NRR, sales efficiency, growth accounting, and executive dashboards. Use when creating metrics dashboards, board reports, revenue reviews, operating cadence, or diagnosing growth constraints.
deliverability-monitoring
Monitor outbound deliverability health across domains, inboxes, DNS, bounces, spam placement, reply rates, and reputation signals. Produces alert thresholds, dashboard spec, weekly QA checklist, and remediation playbook. Use when inboxing drops, bounce rates rise, campaigns underperform, or new infrastructure launches.
tracking-plan
Master analytics tracking plan for PLG and B2B SaaS — unified event taxonomy, pixel strategy (1P and 3P tagging), marketing attribution architecture, CDP implementation (Segment, Rudderstack), product analytics (Amplitude, Mixpanel, PostHog), CRM tracking (HubSpot, Salesforce), and analytics infrastructure design. Use…