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 agentmods add skills/mrkooblu/semrush-mcp/semrush-clinpx skills add mrkooblu/semrush-mcp --skill semrush-cligit clone --depth 1 https://github.com/mrkooblu/semrush-mcpWhat 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 | $0.00025 | $0.01818 |
| Opus 5 | $0.00013 | $0.00909 |
| Sonnet 5 | $0.00005 | $0.00364 |
| Haiku 4.5 | $0.00003 | $0.00182 |
Grade A, and why
semrush-cli 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 3d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEMrush CLI (Local)
Fast keyword research, domain analytics, backlinks, traffic analysis, and competitive intelligence using the locally installed semrush CLI. This CLI is built from the unified semrush-mcp repo and shares the same API client as the MCP server.
Arguments
$ARGUMENTS
- A keyword, domain, or command to run (e.g., "seo tools", "example.com", "kw seo --related")
- If blank, will prompt for a target
Prerequisites
The CLI is installed globally from the semrush-mcp repo. Verify it's available:
semrush --version
Ensure SEMRUSH_API_KEY is set in your environment or .env file.
Available Commands
1. Quick Overview
Auto-detects whether the target is a keyword or domain and returns the appropriate overview.
semrush q "seo tools" # Keyword overview
semrush q example.com # Domain overview
semrush quick "content marketing" -d uk # Specify database
Options:
-d, --database <db>: Country database code (default: us)-f, --format <fmt>: Output format — text or json (default: text)
2. Keyword Research
In-depth keyword analysis with multiple sub-commands.
# Basic keyword overview
semrush kw "content marketing"
# Related keywords
semrush kw "seo" --related -l 20
# Question-based keywords
semrush kw "marketing" --questions -l 10
# Broad match keywords
semrush kw "email marketing" --broad -l 15
# SERP organic results (who ranks for this keyword)
semrush kw "seo tools" --organic -l 10
# SERP paid results
semrush kw "ppc software" --paid -l 10
Options:
--related: Get related keywords--questions: Get question-based keyword variations--broad: Get broad match keywords--organic: Get organic SERP results for the keyword--paid: Get paid SERP results for the keyword-d, --database <db>: Country database code (default: us)-l, --limit <n>: Number of results to return-f, --format <fmt>: Output format — text or json (default: text)
3. Batch Keyword Difficulty
Analyze difficulty scores for multiple keywords at once.
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.
- 3d ago First seen · 253 lines · 25 tokens per session scan A 5ff5a46b2ada
semrush-cli is a skill published in the GitHub repository mrkooblu/semrush-mcp (39 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 1,818 once invoked, about $0.0001 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…