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 commands/cafreeman/foundry-mcp/foundry_create_projectgit 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/commands/cafreeman/foundry-mcp/foundry_create_project)<a href="https://agentmods.dev/commands/cafreeman/foundry-mcp/foundry_create_project"><img src="https://agentmods.dev/badge/commands/cafreeman/foundry-mcp/foundry_create_project.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 | $0.00000 | $0.01270 |
| Opus 5 | $0.00000 | $0.00635 |
| Sonnet 5 | $0.00000 | $0.00254 |
| Haiku 4.5 | $0.00000 | $0.00127 |
Grade A, and why
foundry_create_project 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 3d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Foundry Project
Overview
Create a new Foundry project with comprehensive context documents through collaborative design process.
Context Gathering Phase
Project Portfolio Management:
- Foundry System Check: Use list_projects to avoid naming conflicts and understand existing project portfolio
- Project Name Validation: Ensure kebab-case format for consistency across Foundry system
- Scope Definition: Establish clear boundaries and initial feature set for focused development
Comprehensive Interview Workflow
Phase 1: Problem & Market Context
Core Problem Analysis:
- What specific user pain point or business problem does this project address?
- How do users currently solve this problem, and what are the limitations?
- What would success look like for both users and the business?
- Are there existing solutions, and how would this be different/better?
Target Audience Deep Dive:
- Who are the primary users and what are their technical skill levels?
- What are their key workflows and usage patterns?
- What are their most important requirements and constraints?
- How do they currently discover and adopt new solutions?
Phase 2: Technical Foundation
Technology Preferences & Constraints:
- What programming languages and frameworks are preferred by the team?
- Are there existing infrastructure or platform requirements to consider?
- What are the performance, security, or compliance constraints?
- What is the team's technical expertise and preferred development tools?
Architecture & Integration:
- Will this integrate with existing systems or be standalone?
- What are the expected scale and performance requirements?
- Are there specific API or data integration requirements?
- What deployment environments are planned (cloud, on-premise, hybrid)?
Phase 3: Project Planning
Development Approach:
- What is the development timeline and resource availability?
- Should this be built in phases, and what would the MVP include?
- What are the key risks and how might they be mitigated?
- How will success be measured and validated?
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.
- 3d ago First seen · 135 lines · 0 tokens per session scan A 6ff4a9e39f3b
foundry_create_project is a command published in the GitHub repository cafreeman/foundry-mcp (4 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,270 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.