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.
git clone --depth 1 https://github.com/lirantal/agent-rulesWrote 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/mcp/lirantal/agent-rules/snyk-security)<a href="https://agentmods.dev/mcp/lirantal/agent-rules/snyk-security"><img src="https://agentmods.dev/badge/mcp/lirantal/agent-rules/snyk-security/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/mcp/lirantal/agent-rules/snyk-security"><img src="https://agentmods.dev/badge/mcp/lirantal/agent-rules/snyk-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
Snyk Security 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.
What it actually says
{
"Snyk Security": {
"command": "npx",
"args": [
"-y",
"snyk@latest",
"mcp",
"-t",
"stdio"
],
"trust": true
}
}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 · 13 lines scan A c21e0d45d935
Snyk Security is an MCP server published in the GitHub repository lirantal/agent-rules (62 stars, last pushed 2d ago), licensed Apache-2.0. 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-09-07.
Other mcp servers, from other repositories
crmy
CRMy CLI — Local CLI + stdio MCP server. Runs locally from the @crmy/cli npm package.
fedlex-sparql
MCP server "fedlex-sparql", hosted remotely at mcp.bettercallclaude.ch, as configured in fedec65/bettercallclaude.
nightgate-mcp
MCP server exposing NIGHTGATE (Midnight blockchain attestation layer) to AI agents. Runs locally from the @odatano/nightgate-mcp npm package.
academic-research-mcp-suite
A comprehensive Model Context Protocol (MCP) server suite for academic research workflow automation. Includes 6 specialized servers for complete research pipeline from question refinement to report generation. Runs locally from the academic-research-mcp-suite npm package.
postgres
MCP server "postgres" as configured in latestaiagents/agent-skills. Runs locally from the @anthropic/mcp-postgres npm package. Needs 1 environment variable to run.
urlcheck-mcp
PreClick scans links for threats and confirms intent match with high accuracy before agents click. Remote server at urlcheck.ai.