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 matellez/claude-skills --skill intent-data-activationgit clone --depth 1 https://github.com/matellez/claude-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/matellez/claude-skills/intent-data-activation)<a href="https://agentmods.dev/skills/matellez/claude-skills/intent-data-activation"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/intent-data-activation/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/matellez/claude-skills/intent-data-activation"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/intent-data-activation.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.00238 | $0.01542 |
| Opus 5.5 | $0.00095 | $0.00617 |
| Sonnet 5.5 | $0.00048 | $0.00308 |
| Haiku 4.5 | $0.00024 | $0.00154 |
Grade A, and why
intent-data-activation 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.
This is a copy
100% identical to intent-data-activation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent Data Activation: Turning Signals Into Actions That Generate Pipeline
Intent data earns its cost when it changes what happens next for a specific account. A signal without a workflow is just data. This skill encodes the workflow design decisions that connect a signal to a response, the threshold logic that determines which signals are worth acting on, the routing decisions that determine whether a signal goes to a rep or a campaign, and the measurement framework that tells you whether the activation is working.
HOW TO SET UP THIS SKILL
Provide:
- Which intent data provider or providers you have: ZoomInfo Intent, Bombora, G2 Buyer Intent, 6sense, Demandbase, or other
- Your CRM: HubSpot, Salesforce, or other
- How intent data currently flows into your CRM, if at all
- Whether you have an SDR or BDR team handling outbound
- Your current ICP: the firmographic and behavioral profile of your best-fit accounts
- What, if anything, you are currently doing with intent signals
The Core Problem: Intent Data Without Activation Logic
Intent signals decay fast. A Bombora Company Surge score that spikes on a Monday and is not acted on by Wednesday has already lost significant value. Accounts in active research mode are evaluating multiple vendors simultaneously. The team that responds first with relevant messaging wins more conversations than the team with the best product but the slowest activation.
Step 1: Signal Triage Before Building Any Workflow
Signal quality by source type:
First-party signals (your own website, your own HubSpot or Salesforce data): Highest quality. An account visiting your pricing page three times in a week is a more reliable signal than an account showing Bombora surge on a topic adjacent to your category.
G2 Buyer Intent: High quality for software categories. An account actively reviewing products in your category on G2 has demonstrated vendor evaluation behavior.
Bombora Company Surge: Medium quality. Topic selection matters enormously. Broad topics produce noise. Narrow, category-specific topics produce signal.
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 · 147 lines · 238 tokens per session scan A 1ee9acca3153
intent-data-activation is a skill published in the GitHub repository matellez/claude-skills (4 stars, last pushed 6mo ago), licensed MIT. It adds 238 tokens to every session and 1,542 once invoked, about $0.0010 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to intent-data-activation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.
rudder-instrumentation-debugging
Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.
rudder-ai-events-verify
Verifies RudderStack AI events locally: captures what an instrumented app or MCP server sends, validates it against the AI events v0.3 schema, and checks joins, counts, identity and content. Use when testing AI events, or when AI or MCP events look wrong or missing.
helius
Skill "helius" from helius-labs/core-ai, covering helius — build on solana, prerequisites, 1. helius mcp server, 2. mcp router surface and 3. api key.