Borrowing it
Nothing to install: this file belongs to jain-eshan/google-trends-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jain-eshan/google-trends-mcp/main/.claude/skills/trends/SKILL.mdgit clone --depth 1 https://github.com/jain-eshan/google-trends-mcpWrote 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/jain-eshan/google-trends-mcp/trends)<a href="https://agentmods.dev/skills/jain-eshan/google-trends-mcp/trends"><img src="https://agentmods.dev/badge/skills/jain-eshan/google-trends-mcp/trends/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/jain-eshan/google-trends-mcp/trends"><img src="https://agentmods.dev/badge/skills/jain-eshan/google-trends-mcp/trends.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.00051 | $0.00436 |
| Opus 5 | $0.00026 | $0.00218 |
| Sonnet 5 | $0.00010 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
trends 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.
What it actually says
Trends Research
Use the google-trends MCP tools to research $ARGUMENTS and synthesize the findings. The tools return raw data only — no interpretation — so the synthesis happens here, in this skill.
What to pull
Not every tool applies to every topic — call the ones that make sense, skip the rest.
- interest_over_time — compare the core keyword(s) for the topic over the last 12 months (
geo="IN"by default, unless the request implies otherwise). Note direction (rising/falling/flat), and flag if the latest point hasisPartial: true— that value is provisional, don't read it as a real drop. - related_queries — what people search alongside the core keyword. A "rising" value of
5000%is Google's "Breakout" marker (explosive growth from near-zero), not a literal percentage — call that out as the strongest signal of an emerging sub-trend, not a number to quote. - related_topics — same idea, but topic clusters instead of raw query strings — useful for spotting adjacent categories the user might not have thought to search for directly.
- interest_by_region — where interest concentrates, if geography is relevant to the question being asked.
- trending_now — only call this for an explicit "what's hot right now" question, not general interest research. Known limitation: this one currently fails (Google retired the endpoint it depends on) — that's expected, not a bug, and no reason to skip the other tools.
Output
Plain-language summary: is interest growing or shrinking, what's driving it (related queries/topics), where it's concentrated, and any breakout signals worth flagging. Don't just dump raw numbers — say what they mean for the actual question being asked.
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 · 23 lines · 51 tokens per session scan A 8753761f2b00
trends is a skill published in the GitHub repository jain-eshan/google-trends-mcp (1 stars, last pushed 20d ago), licensed MIT. It adds 51 tokens to every session and 436 once invoked, about $0.0003 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-31.
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…