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 instructions/mrkooblu/semrush-mcp/claude-mdgit clone --depth 1 https://github.com/mrkooblu/semrush-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/instructions/mrkooblu/semrush-mcp/claude-md)<a href="https://agentmods.dev/instructions/mrkooblu/semrush-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/mrkooblu/semrush-mcp/claude-md.svg" alt="Measured on agentmods" 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.00920 | $0.00920 |
| Opus 5 | $0.00460 | $0.00460 |
| Sonnet 5 | $0.00184 | $0.00184 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
semrush-mcp CLAUDE.md 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 5d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code when working with code in this repository.
Project Overview
semrush-mcp is a unified Semrush MCP server and CLI for keyword research, domain analytics, backlinks, traffic analysis, and competitive intelligence. It provides two entry points that share the same API client:
semrush-mcp— MCP server (stdio transport) for AI clients (Claude, Cursor, etc.)semrush— CLI for direct terminal usage
Commands
# Development
npm install # Install dependencies
npm run build # Build TypeScript to dist/
npm run dev # Start MCP server in dev mode (tsx)
npm run start # Start built MCP server
# Testing
npm test # Run all tests
npm run test:unit # Unit tests only (mocked, no API key needed)
npm run test:integration # Integration tests (requires SEMRUSH_API_KEY)
# Quality
npm run lint # ESLint
npm run format # Prettier format
Git Hooks
Pre-commit and pre-push hooks are installed via Husky.
Pre-commit runs:
- lint-staged (prettier + eslint auto-fix on staged .ts files)
- ESLint (full lint pass)
- TypeScript type-check (
tsc --noEmit) - Unit tests (excludes integration tests)
- Secret detection (scans for hardcoded API keys/tokens)
Pre-push runs:
- Uncommitted changes check
- Full build (
npm run build) - Integration tests (requires
SEMRUSH_API_KEY)
Architecture
src/
├── index.ts # MCP server entry point (McpServer API)
├── cli.ts # CLI entry point (Commander.js)
├── semrush-api.ts # Shared API client (singleton via lazy Proxy)
├── schemas.ts # Zod validation schemas + inferred TS types
├── config.ts # Configuration, logger, env loading
└── __tests__/ # Test suite (unit + integration)
Key patterns:
semrushApiis a lazy Proxy singleton — import it, never constructSemrushApiClientdirectly (except in tests)- The API client handles retries (429/5xx), caching, and rate limiting internally
SemrushApiErrorhas.statusand.responsefields for error handling
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.
- 5d ago First seen · 105 lines · 920 tokens per session scan A 4fab2a618635
semrush-mcp CLAUDE.md is an instructions file published in the GitHub repository mrkooblu/semrush-mcp (39 stars, last pushed 5mo ago), licensed MIT. It adds 920 tokens to every session, about $0.0046 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).