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 mcp/shanraisshan/claude-code-best-practice/context7git clone --depth 1 https://github.com/shanraisshan/claude-code-best-practiceGrade A, and why
context7 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 2d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- context7 — 100% identical, 2 lines differ
- context7 — 100% identical, 2 lines differ
- context7 — 100% identical, 2 lines differ
- Context7 — 100% identical, 4 lines differ
- context7 — 100% identical, 2 lines differ
- context7 — 100% identical, 2 lines differ
- context7 — 100% identical, 2 lines differ
- context7 — 100% identical, 2 lines differ
What it actually says
{
"context7": {
"command": "npx",
"args": [
"-y",
"@upstash/[email protected]"
]
}
}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.
- 2d ago First seen · 9 lines scan A e35e4e0cc0e7
context7 is an MCP server published in the GitHub repository shanraisshan/claude-code-best-practice (65,460 stars, last pushed today), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
elicit
Elicitation MCP server. Runs locally from the @blizzy/mcp-elicit npm package.
figma-desktop
A Model Context Protocol Server that runs as stdio, wrapping a Streamable HTTP server, so any MCP-supporting client can use Streamable HTTP MCP Servers. Runs locally from the @pyroprompts/mcp-stdio-to-streamable-http-adapter npm package. Needs 1 environment variable to run.
chrome-devtools
MCP server "chrome-devtools", hosted remotely at 127.0.0.1, as configured in L-X-T/ng-agentic.
patch-file-mcp
An MCP Server to patch existing files. Runs locally from the patch-file-mcp Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.