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 skills add antimetal/cursor-plugin --skill antimetal-mcp-setupgit clone --depth 1 https://github.com/antimetal/cursor-pluginWrote 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/skills/antimetal/cursor-plugin/antimetal-mcp-setup)<a href="https://agentmods.dev/skills/antimetal/cursor-plugin/antimetal-mcp-setup"><img src="https://agentmods.dev/badge/skills/antimetal/cursor-plugin/antimetal-mcp-setup.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.00048 | $0.00516 |
| Opus 5 | $0.00024 | $0.00258 |
| Sonnet 5 | $0.00010 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade B, and why
antimetal-mcp-setup scanned grade B with 1 finding 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 8d 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
The Antimetal MCP server authenticates via an API key sent in the `Authorization` header. The plugin's MCP configuration (`../../mcp.json` relative to this file) references the `ANTIMETAL_API_KEY` environment variable. I What it actually says
Antimetal MCP Setup
You are the gatekeeper. Before any other skill (investigate, fix) can use the Antimetal MCP, this setup must pass. Do not attempt to list or call MCP tools until it does.
How It Works
The Antimetal MCP server authenticates via an API key sent in the Authorization header. The plugin's MCP configuration (../../mcp.json relative to this file) references the ANTIMETAL_API_KEY environment variable. If this variable is missing or empty, every MCP request will fail silently.
Setup Checklist
-
Read the MCP config. Open
../../mcp.json(the grandparent directory of this skill) and confirm it referencesANTIMETAL_API_KEYin the authorization header. -
Verify the API key is set. Check whether
ANTIMETAL_API_KEYexists in the environment.- If it's set: skip ahead -- you're good to go.
- If it's not set: stop here. Walk the user through getting one:
- Sign up or log in at antimetal.com
- Generate an API key from account settings
- Add it to their shell profile:
export ANTIMETAL_API_KEY="am_..." - Source the profile or restart the terminal, then reload the Cursor window via the Command Palette (
⌘⇧Pon Mac,Ctrl+Shift+Pon Windows/Linux) → Reload Window
Do not proceed past this step without a valid key. Do not check tool schemas, do not attempt MCP calls. The user must provide the key first.
-
Hand off. Once the key is confirmed, continue to whichever skill the user needs -- investigate or fix.
What This Skill Is NOT
This skill configures the connection. It does not:
- Search for issues or answer questions (that's investigate)
- Do root cause analysis (that's investigate)
- Apply code changes (that's fix)
If setup passes, get out of the way and let the right skill take over.
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.
- 8d ago First seen · 43 lines · 48 tokens per session scan B 137e3aa6c771
antimetal-mcp-setup is a skill published in the GitHub repository antimetal/cursor-plugin (1 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 516 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
Incident Response Planner
Analyze an infrastructure incident alert and produce a structured response plan plus an executable on-call runbook. Use for incident, alert, on-call, and runbook requests.
setup-environment-profile
Point the ilert CLI at a staging, preview or self-hosted ilert environment by giving it its own profile.
ilert-essentials
Core ilert concepts and CLI behaviour: the object model and the rules behind the field names.
migrate-from-opsgenie
Map Opsgenie resources onto ilert equivalents.
migrate-from-pagerduty
Map PagerDuty resources onto ilert equivalents.
migrate-from-statuspageio
Map Statuspageio (Atlassian Statuspage) resources onto ilert status page equivalents.