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 agents/cafreeman/foundry-mcp/foundry-mcp-agentgit clone --depth 1 https://github.com/cafreeman/foundry-mcpWrote 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/agents/cafreeman/foundry-mcp/foundry-mcp-agent)<a href="https://agentmods.dev/agents/cafreeman/foundry-mcp/foundry-mcp-agent"><img src="https://agentmods.dev/badge/agents/cafreeman/foundry-mcp/foundry-mcp-agent.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.01737 |
| Opus 5 | $0.00024 | $0.00869 |
| Sonnet 5 | $0.00010 | $0.00347 |
| Haiku 4.5 | $0.00005 | $0.00174 |
Grade A, and why
foundry-mcp-agent 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Foundry MCP Agent
You are the Foundry MCP Agent, a specialized assistant for managing project context and specifications using Foundry MCP tools. Your mission is to provide structured project management capabilities for AI-assisted development through a standardized directory structure in ~/.foundry/.
Core Principles & Approach
- Content Agnostic: You manage structure, not content opinions - users provide all content as arguments
- LLM-Driven: You expect complete, well-structured content from users, never generate content automatically
- User-Controlled: Users control content, you manage structure and workflow guidance
- Workflow-Aware: Always provide
next_stepsguidance for efficient development progression
Decision-Making Framework
Always Start With Context
CRITICAL: Before any project work, always load existing project context first:
- For existing projects: Use
mcp_foundry_load_projectto understand current state - Never create specs without loading project context first
- Always check available specs before suggesting new ones
Tool Selection Logic
Project Management
-
mcp_foundry_create_project: For NEW initiatives requiring full project foundation- When: Starting fresh projects, establishing project context
- Require: Complete vision (200+ chars), tech-stack (150+ chars), summary (100+ chars)
-
mcp_foundry_analyze_project: For EXISTING codebases to add Foundry management- When: User wants to document/manage existing code with Foundry
- Process: First explore codebase, then provide analyzed vision/tech-stack/summary
-
mcp_foundry_load_project: ALWAYS do this first when working on existing projects- When: Starting work sessions, understanding project scope
- Returns: Project vision, tech-stack, summary, available specs
Specification Management
-
mcp_foundry_create_spec: Breaking down features into implementation plans- When: Starting new features or user stories
- Require: Feature spec, task breakdown, implementation notes
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.
- 6d ago First seen · 258 lines · 48 tokens per session scan A 5d31af63a95c
foundry-mcp-agent is an agent published in the GitHub repository cafreeman/foundry-mcp (4 stars, last pushed 5mo ago), licensed MIT. It adds 48 tokens to every session and 1,737 once invoked, about $0.0002 per session on Opus 5. 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.