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 anysiteio/agent-skills --skill anysite-crm-inboundgit clone --depth 1 https://github.com/anysiteio/agent-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/anysiteio/agent-skills/anysite-crm-inbound)<a href="https://agentmods.dev/skills/anysiteio/agent-skills/anysite-crm-inbound"><img src="https://agentmods.dev/badge/skills/anysiteio/agent-skills/anysite-crm-inbound/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/anysiteio/agent-skills/anysite-crm-inbound"><img src="https://agentmods.dev/badge/skills/anysiteio/agent-skills/anysite-crm-inbound.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00127 | $0.00913 |
| Opus 5 | $0.00063 | $0.00456 |
| Sonnet 5 | $0.00025 | $0.00183 |
| Haiku 4.5 | $0.00013 | $0.00091 |
Grade A, and why
anysite-crm-inbound 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRM Inbound — one lead, one minute
Every skill in this pack is batch-shaped except the most frequent moment in GTM life: a single lead just landed and someone asks "is this real / are they our ICP / who takes the call?". This skill answers that in 2 calls (verdict) to 4–5 calls (full mini-brief). Strictly read-only.
Input
Whatever the user has: an email, a name + company, a linkedin_url, or a forwarded demo-request text. Extract identifiers yourself; don't interrogate the user.
Flow (cheap-first, stop as soon as the verdict is clear)
1. Identify the person and company
- linkedin_url →
execute linkedin/user/user {user: <url>}→ done. - email with a work domain → resolve the company by domain (anysite-mcp recipe: exact
verify;
webparser/parsefallback for common-token domains) →organizational_urn→search_users {first_name, last_name, current_company: [{"type": "company", "value": "<id>"}]}. Note:email_sql_userreverse lookup is a cheap first try but verified to miss often — don't stop on its empty result. - email with a personal domain (gmail etc.) → reverse lookup try, else name+company if the form/message carries them. A lead reachable ONLY via personal email = flag it.
- name + company → resolve company →
search_userswith the company filter (bare names return namesakes).
2. Company reality check (1 call, often already done in step 1)
The verified search_sql_companies row gives industry, employee_count, locations,
description, crunchbase_link, organizational_urn. Funding stage matters →
crunchbase/company via the free alias from crunchbase_link (skip for obviously
non-venture companies).
3. CRM history (free, crm_* reads)
crm_query_records(object_type="contacts", emails=[...]) # known already?
crm_query_records(object_type="companies", search="<domain>") # account history?
Existing record with an owner → this is a routing question, not a research question; say who owns it. Closed-lost history → the verdict must mention it.
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.
- 12d ago First seen · 69 lines · 127 tokens per session scan A fa8df2c18be2
anysite-crm-inbound is a skill published in the GitHub repository anysiteio/agent-skills (19 stars, last pushed 27d ago), licensed MIT. It adds 127 tokens to every session and 913 once invoked, about $0.0006 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…