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-mcp-migrationgit 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-mcp-migration)<a href="https://agentmods.dev/skills/anysiteio/agent-skills/anysite-mcp-migration"><img src="https://agentmods.dev/badge/skills/anysiteio/agent-skills/anysite-mcp-migration/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-mcp-migration"><img src="https://agentmods.dev/badge/skills/anysiteio/agent-skills/anysite-mcp-migration.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.00121 | $0.03565 |
| Opus 5 | $0.00060 | $0.01783 |
| Sonnet 5 | $0.00024 | $0.00713 |
| Haiku 4.5 | $0.00012 | $0.00357 |
Grade A, and why
anysite-mcp-migration 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 11d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
anysite MCP Migration Assistant
Migrate your anysite MCP skills, prompts, and agent instructions from v1 (individual tools) to v2 (universal meta-tools).
Overview
Anysite MCP v2 replaces 70+ individual tools with 5 universal meta-tools. This skill helps you:
- Rewrite tool references from old format (
search_linkedin_users,get_linkedin_profile) to newexecute()calls - Add new v2 capabilities like pagination, server-side filtering, aggregation, and file export
- Validate migrated output to ensure nothing was missed
- Preserve workflow logic while updating only the tool interface layer
When to Use
- User says "migrate my skill to v2", "update for new anysite API", "convert to execute format"
- User pastes a skill or prompt that contains old-style tool names (
search_*,get_*,find_*) - User asks how to use new anysite MCP features (pagination, cache queries, export)
Migration Workflow
Step 1: Receive Input
Ask the user for one of:
- A skill file path — read the SKILL.md and any files in
references/ - Pasted prompt text — the raw text of their prompt or instruction
- A description of what the skill does — you'll help build it from scratch using v2 format
Step 2: Identify Old Tool References
Scan the input for any of these v1 tool name patterns:
| Pattern | Example |
|---|---|
search_linkedin_* |
search_linkedin_users, search_linkedin_companies, search_linkedin_jobs, search_linkedin_posts |
get_linkedin_* |
get_linkedin_profile, get_linkedin_company, get_linkedin_user_posts |
find_linkedin_* |
find_linkedin_email, find_linkedin_user_email |
google_linkedin_* |
google_linkedin_search |
search_twitter_* / get_twitter_* |
search_twitter_users, get_twitter_user, get_twitter_user_tweets |
search_instagram_* / get_instagram_* |
search_instagram_users, get_instagram_user, get_instagram_post |
search_youtube_* / get_youtube_* |
search_youtube, get_youtube_channel, get_youtube_video |
search_reddit_* / get_reddit_* |
search_reddit, get_reddit_user, get_reddit_posts |
search_yc_* / get_yc_* |
search_yc_companies, get_yc_company |
search_sec_* / get_sec_* |
search_sec_filings, get_sec_document |
scrape_webpage |
scrape_webpage |
mcp__anysite__* |
Any tool with the MCP prefix — strip prefix and match above |
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.
- 11d ago First seen · 291 lines · 121 tokens per session scan A ccddf2b0eef9
anysite-mcp-migration is a skill published in the GitHub repository anysiteio/agent-skills (19 stars, last pushed 26d ago), licensed MIT. It adds 121 tokens to every session and 3,565 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…