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/bifrost5/foundryWrote 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/rules/bifrost5/foundry/mcp)<a href="https://agentmods.dev/rules/bifrost5/foundry/mcp"><img src="https://agentmods.dev/badge/rules/bifrost5/foundry/mcp/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/rules/bifrost5/foundry/mcp"><img src="https://agentmods.dev/badge/rules/bifrost5/foundry/mcp.svg" alt="Reviewed on agentmods" width="80" 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.00003 | $0.00034 |
| Opus 5.5 | $0.00001 | $0.00014 |
| Sonnet 5.5 | $0.00001 | $0.00007 |
| Haiku 4.5 | $0.00000 | $0.00003 |
Grade A, and why
mcp 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 today.
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.
This is a copy
100% identical to mcp — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
- If I ask to use an MCP and a tool fails report and shut up. Dont proceed.
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.
- today First seen · 5 lines · 3 tokens per session scan A 7ab82f94e2fc
mcp is a cursor rule published in the GitHub repository bifrost5/foundry (12 stars, last pushed 3mo ago), licensed MIT. It adds 3 tokens to every session and 34 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to mcp, differing in 0 lines, and is treated as a copy.
mcp compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| mcpbifrost5/foundry | Cursor rule | 12 | 3mo ago | MIT | A | 3 | Cursor |
| contextsai-supervisor-foundry/foundry | Cursor rule | 12 | 3mo ago | MIT | A | 5 | Cursor |
| supervisor-specsai-supervisor-foundry/foundry | Cursor rule | 12 | 3mo ago | MIT | A | 167 | Cursor |
| cleanupai-supervisor-foundry/foundry | Cursor rule | 12 | 3mo ago | MIT | A | 9 | Cursor |
| secretsai-supervisor-foundry/foundry | Cursor rule | 12 | 3mo ago | MIT | A | 4 | Cursor |
| task-lifecycleai-supervisor-foundry/foundry | Cursor rule | 12 | 3mo ago | MIT | A | 32 | Cursor |
| docsai-supervisor-foundry/foundry | Cursor rule | 12 | 3mo ago | MIT | A | 23 | Cursor |