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-setupgit 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-setup)<a href="https://agentmods.dev/skills/anysiteio/agent-skills/anysite-crm-setup"><img src="https://agentmods.dev/badge/skills/anysiteio/agent-skills/anysite-crm-setup/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-setup"><img src="https://agentmods.dev/badge/skills/anysiteio/agent-skills/anysite-crm-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 9 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 38 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Agent Snooping · line 88 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 128 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00135 | $0.02217 |
| Opus 5 | $0.00068 | $0.01108 |
| Sonnet 5 | $0.00027 | $0.00443 |
| Haiku 4.5 | $0.00014 | $0.00222 |
Grade A, and why
anysite-crm-setup 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Anysite CRM Setup
Connect the user's CRM and produce a local CRM profile — a saved field mapping that makes every future enrichment write deterministic: the same data always lands in the same CRM properties.
When to use
- First-time setup: "connect my HubSpot", "connect my Pipedrive", "set up CRM enrichment"
- Re-discovery: CRM schema changed, mapping feels stale, or writes are being skipped unexpectedly
- Reference: the Writing rules section below applies to EVERY session that calls
crm_upsert_contacts/crm_upsert_companies, even outside setup
Prerequisites
The crm_* tools are visible only when the user has enabled CRM integration in their Anysite
dashboard (Profile → CRM Integration). If the tools are missing, ask the user to enable it there.
After they enable it, the tools do NOT appear instantly: the server flag takes up to a minute to
propagate, and the agent's tool list is cached per session — ask the user to reconnect the MCP
server (or start a new session), then retry. This is expected behavior, not an error.
Setup flow
1. Ensure a connection
Call crm_list_connections.
- If there is an active connection — proceed to step 2.
- If not, ask which CRM the user wants (HubSpot or Pipedrive) if not obvious, then call
crm_connect(provider="hubspot")orcrm_connect(provider="pipedrive"), give the user theconnect_urlto open in a browser, then pollcrm_connect_status(pending_id)every few seconds untilactive. - Only ONE CRM can be connected at a time. If
crm_connectreturns a conflict, the user must disconnect the current CRM in the dashboard first — never disconnect for them without asking.
2. Read the schema
Call crm_get_schema(). You get:
properties.contacts/properties.companies— every property withlabel,type,options(valid enum values),read_only,customlists— the user's CRM lists (id, name, processing type)protected_properties— fields the server will never let you write
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 · 169 lines · 135 tokens per session scan A 211d4ec8d717
anysite-crm-setup is a skill published in the GitHub repository anysiteio/agent-skills (19 stars, last pushed 27d ago), licensed MIT. It adds 135 tokens to every session and 2,217 once invoked, about $0.0007 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…