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_list_specsgit 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_list_specs)<a href="https://agentmods.dev/commands/cafreeman/foundry-mcp/foundry_list_specs"><img src="https://agentmods.dev/badge/commands/cafreeman/foundry-mcp/foundry_list_specs.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.00000 | $0.01016 |
| Opus 5 | $0.00000 | $0.00508 |
| Sonnet 5 | $0.00000 | $0.00203 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
foundry_list_specs 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 5d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
List Specs With Foundry
Overview
Discover and analyze existing specifications for a project to guide development planning and prioritization.
Context Gathering Phase
Project Discovery & Validation:
- Parameter Resolution: If project name missing, use list_projects to show available options and guide selection
- Project Context: Load project summary if available to understand domain and development scope
- System Validation: Ensure project exists in Foundry system before attempting spec listing
Comprehensive Discovery Workflow
Step 1: Project Resolution
Missing Project Name Handling:
- Execute list_projects to display available Foundry projects with metadata
- Present projects in user-friendly format with creation dates and brief descriptions
- Guide user to select appropriate project for spec exploration
Project Validation:
- Confirm target project exists and is accessible
- Load basic project context (vision/summary) if available for user orientation
- Set expectations about spec discovery process
Step 2: Specification Listing & Analysis
Execute Spec Discovery:
{"name":"list_specs","arguments":{"project_name":"$1"}}
Results Processing & Presentation:
- Chronological Organization: Present specs with newest first to show development progression
- Metadata Display: Include spec names, feature names, creation dates, and brief purpose descriptions
- Status Assessment: Highlight incomplete or recently modified specs for priority attention
- Categorization: Group by development phase, feature area, or completion status when patterns emerge
Step 3: Development Insights & Analysis
Spec Portfolio Assessment:
- Project Maturity: Evaluate development progress based on spec count and completion patterns
- Feature Coverage: Identify areas with comprehensive specifications vs gaps needing attention
- Development Velocity: Note patterns in spec creation and modification timing
- Priority Identification: Highlight specs with incomplete tasks or recent activity
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.
- 5d ago First seen · 105 lines · 0 tokens per session scan A 419c8bb8be8e
foundry_list_specs 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,016 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.