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/iloveitaly/llm-ide-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/iloveitaly/llm-ide-rules/terraform)<a href="https://agentmods.dev/mcp/iloveitaly/llm-ide-rules/terraform"><img src="https://agentmods.dev/badge/mcp/iloveitaly/llm-ide-rules/terraform/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/iloveitaly/llm-ide-rules/terraform"><img src="https://agentmods.dev/badge/mcp/iloveitaly/llm-ide-rules/terraform.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
terraform 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 1mo 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
{
"terraform": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"hashicorp/terraform-mcp-server"
]
}
}What else mcp.json configures
This page is one entry in a file that holds 7. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 11 lines scan A 7e0a9bcf47db
terraform is an MCP server published in the GitHub repository iloveitaly/llm-ide-rules (13 stars, last pushed 4d ago), 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-09-06.
Other mcp servers, from other repositories
seqera
MCP server "seqera", hosted remotely at mcp.seqera.io, as configured in nextflow-io/agent-skills.
scrapebadger
MCP server for ScrapeBadger - Twitter/X scraping API for AI agents. Runs locally from the scrapebadger-mcp Python package. Needs 1 environment variable to run.
s3
AWS S3 MCP — list buckets, browse objects, upload/download, presigned URLs. Runs locally from the mcp-server-s3 npm package.
azure-finops-mcp
MCP server exposing Azure FinOps capabilities to LLM clients. Runs locally from the azure-finops-mcp Python package. Needs 3 environment variables to run.
prompteka-mcp
Model Context Protocol server for Prompteka - enables AI assistants to read and write prompts. Runs locally from the prompteka-mcp npm package.
mcp
Detect prompt injection, jailbreaks, and code injection in untrusted text before it reaches an LLM. Runs locally from the @safeprompt.dev/mcp npm package. Needs 3 environment variables to run.