clay-buying-signals-5

clay-buying-signals-5 is a skill for Claude Code, Codex from swan-gtm/gtm-skills. It costs 45 tokens per session (839 once invoked), scanned A, original, MIT.

A guide to five buying signals for Clay, a tool for building data and outreach workflows. Buying signals are events suggesting that a company may soon need or consider a product.

In plain words
What is it for?
Use it to build Clay workflows around job changes, hiring, website visits, funding announcements, and technology changes.
Why use it?
It helps sales teams decide whom to contact and when, instead of sending the same outreach to every company.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to build Clay workflows around job changes, hiring, website visits, funding announcements, and technology changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/swan-gtm/gtm-skills/clay-buying-signals-5
Install

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.

Any agent
npx skills add swan-gtm/gtm-skills --skill clay-buying-signals-5
Clone the repo
git clone --depth 1 https://github.com/swan-gtm/gtm-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for clay-buying-signals-5

README.md
[![agentmods](https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/clay-buying-signals-5/github.svg)](https://agentmods.dev/skills/swan-gtm/gtm-skills/clay-buying-signals-5)
Your own site
<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/clay-buying-signals-5"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/clay-buying-signals-5/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.

agentmods 80×15 button for clay-buying-signals-5

Your own site · 80×15
<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/clay-buying-signals-5"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/clay-buying-signals-5.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 839 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00839
Opus 5 $0.00023 $0.00419
Sonnet 5 $0.00009 $0.00168
Haiku 4.5 $0.00005 $0.00084

Measured 12d ago against content hash d6378e9ad6bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

clay-buying-signals-5 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 12d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/alex-vacca/clay-buying-signals-5/SKILL.md · 148 lines

How it starts

The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.

5 Buying Signals for Clay Workflows

1. Recent Job Changes (0-90 days)

Why it works:

  • 3x higher response rate
  • Peak engagement: days 14-45
  • They're actively building their stack

Clay setup:

  • Track LinkedIn job changes
  • Filter by title/seniority
  • Alert within 24 hours of detection

2. Company Hiring for Specific Roles

Why it works:

  • Signals budget allocation
  • Shows growth trajectory
  • Indicates priority areas

Clay setup:

  • Monitor job postings (LinkedIn, Indeed)
  • Filter by relevant roles
  • Track posting volume/velocity

3. Website Visitors

Why it works:

  • 25-30% reply rate (they know you)
  • Highest intent signal
  • Act within 24-48 hours

Clay setup:

  • Integrate RB2B or similar
  • Enrich visitor data
  • Auto-route to outreach sequence

4. Funding Announcements

Why it works:

  • New budget available
  • Mandate for growth spending
  • Reach out 2-4 weeks after

Clay setup:

  • Crunchbase integration
  • Filter by round size
  • Delay outreach 2-4 weeks

5. Technology Changes

Why it works:

  • Active buying window
  • Fresh pain from transition
  • Open to new solutions

Clay setup:

  • BuiltWith integration
  • Track additions/removals
  • Filter by relevant tech

Performance Benchmarks

Outreach Type Reply Rate
Cold outreach 6-8%
Signal-based 18-22%
Multi-signal stacked 35-40%

Signal Workflow Tips

Don't Mention Signal Explicitly

  • Prospects get these constantly
  • Instead, use signal to inform timing and angle
  • Reference the underlying pain, not the trigger

Act Fast

  • Hot signals expire in 3-7 days
  • Job changes: days 14-45 optimal
  • Website visitors: within 24-48 hours

Stack Signals for Heat Scoring

  • 1 signal = Standard priority
  • 2 signals = High priority
  • 3+ signals = Reach out same day

Signal Priority Matrix

Signal Priority Timing Reply Rate
Website visitor Highest <24 hours 25-30%
Job change High Days 14-45 20-25%
Funding Medium-High 2-4 weeks 18-22%
Hiring Medium 1-2 weeks 15-20%
Tech change Medium 1-2 weeks 15-18%

Read the full file on GitHub · 148 lines

Changes

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.

  1. 12d ago First seen · 148 lines · 45 tokens per session scan A d6378e9ad6bf

Subscribe to this mod's changes

clay-buying-signals-5 is a skill published in the GitHub repository swan-gtm/gtm-skills (150 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 839 once invoked, about $0.0002 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.