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 skills/foundry-works/foundry-mcp/foundry-implement-autonpx skills add foundry-works/foundry-mcp --skill foundry-implement-autogit clone --depth 1 https://github.com/foundry-works/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/skills/foundry-works/foundry-mcp/foundry-implement-auto)<a href="https://agentmods.dev/skills/foundry-works/foundry-mcp/foundry-implement-auto"><img src="https://agentmods.dev/badge/skills/foundry-works/foundry-mcp/foundry-implement-auto.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.00054 | $0.02603 |
| Opus 5 | $0.00027 | $0.01301 |
| Sonnet 5 | $0.00011 | $0.00521 |
| Haiku 4.5 | $0.00005 | $0.00260 |
Grade A, and why
foundry-implement-auto 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 4d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
foundry-implement-auto
Purpose
Run exactly one autonomous implementation phase for a spec in unattended mode, then stop deterministically at the phase boundary or any escalation condition.
Reference:
- Runtime contract:
src/foundry_mcp/skills/foundry_implement_auto.py - Supervisor runbook:
docs/guides/autonomy-supervisor-runbook.md - Agent isolation:
docs/guides/autonomy-agent-isolation.md
Flow
[x?]=decision(GATE)=server gate→=sequence↻=loop!=escalation§=section ref
Entry → [spec_id arg present?]
→ [no] → ! SPEC_ID_MISSING → EXIT
→ [yes] → §Preflight (6 checks)
→ [all pass?]
→ [no] → ! FoundryImplementAutoError + remediation → EXIT
→ [yes] → SessionStart
→ [SPEC_SESSION_EXISTS?]
→ [yes] → §SessionReuse → §StaleSessionRecovery (replay probe) → StepLoop
→ [no] → StepLoop (fresh session, no stale steps possible)
→ StepLoop (max 200 iterations) ↻
→ task(session-step, command="next")
→ [loop_signal?]
→ [phase_complete] → EXIT success
→ [spec_complete] → EXIT success
→ [paused|failed|blocked_runtime] → ! EXIT escalation
→ [continue] → Dispatch(next_step.type)
→ [implement_task] → §ImplementTask
→ [execute_verification] → §ExecuteVerification
→ [run_fidelity_gate] → §RunFidelityGate
→ [address_fidelity_feedback] → §AddressFidelityFeedback
→ [pause|complete_spec] → EXIT
→ Report outcome → ↻ StepLoop
→ [max_iterations exceeded] → ! LOOP_LIMIT_EXCEEDED → EXIT
→ Emit exit packet
MCP Tooling
All interactions use the Foundry MCP router+action pattern: mcp__plugin_foundry_foundry-mcp__<router>.
| Router | Key Actions |
|---|---|
task |
session (start/list), session-step (next/report/replay), prepare |
spec |
find |
server |
capabilities |
review |
fidelity-gate |
verification |
execute |
Non-Negotiable Rules
- Zero interaction. Never use
AskUserQuestionor any interactive prompt. This skill runs fully unattended. If any required input is missing (spec_id, environment), emit a structured error and EXIT immediately — do not ask, guess, or offer choices. - Runtime truth only. Use MCP tool responses as the source of truth for feature flags, posture, and role. Never trust discovery metadata or manifest alone.
- Server-driven sequencing. The session-step orchestrator is the sole authority on task ordering, phase boundaries, and gate timing. Never infer or override task sequence.
- No privilege escalation. Never set
allow_lock_bypass=true,allow_gate_waiver=true, or request elevated role. Always passenforce_autonomy_write_lock=trueon session start. - Fail fast on policy violations. Any preflight failure terminates immediately with structured remediation.
- Deterministic exit. Stop on
phase_completeorspec_complete. Escalate on all other terminalloop_signalvalues. Never continue on ambiguous state. - Bounded execution. Hard limit of
max_iterations=200. If exceeded without terminal signal, stop and escalate.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 208 lines · 54 tokens per session scan A 1408a3cddf95
foundry-implement-auto is a skill published in the GitHub repository foundry-works/foundry-mcp (4 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 2,603 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…