foundry-implement-auto

foundry-implement-auto is a skill for Claude Code from foundry-works/foundry-mcp. It costs 54 tokens per session (2,603 once invoked), scanned A, original, MIT.

A controlled runner for carrying out one phase of a software specification through Foundry's session-step process, with checks before work begins and a clear stop at the phase boundary.

In plain words
What is it for?
Use it when an autonomous implementation task has a specification ID and must follow Foundry's session, step, gate, and escalation rules.
Why use it?
It limits unattended implementation to a defined phase and stops when the work is complete, paused, failed, or blocked. This makes the result easier to supervise and verify.

Skill for Claude Code

Written for Claude Code: SessionStart hook event. Also seen: names the AskUserQuestion tool; mentions Claude Code.

Good fit Use it when an autonomous implementation task has a specification ID and must follow Foundry's session, step, gate, and escalation rules.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/foundry-works/foundry-mcp/foundry-implement-auto
Install

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.

Any agent
npx skills add foundry-works/foundry-mcp --skill foundry-implement-auto
Clone the repo
git clone --depth 1 https://github.com/foundry-works/foundry-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for foundry-implement-auto

README.md
[![agentmods](https://agentmods.dev/badge/skills/foundry-works/foundry-mcp/foundry-implement-auto/github.svg)](https://agentmods.dev/skills/foundry-works/foundry-mcp/foundry-implement-auto)
Your own site
<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/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.

agentmods 80×15 button for foundry-implement-auto

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,603 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.02603
Opus 5.5 $0.00022 $0.01041
Sonnet 5.5 $0.00011 $0.00521
Haiku 4.5 $0.00005 $0.00260

Measured 1mo ago against content hash 1408a3cddf95, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

skills/foundry-implement-auto/SKILL.md · 208 lines

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

  1. Zero interaction. Never use AskUserQuestion or 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.
  2. 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.
  3. 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.
  4. No privilege escalation. Never set allow_lock_bypass=true, allow_gate_waiver=true, or request elevated role. Always pass enforce_autonomy_write_lock=true on session start.
  5. Fail fast on policy violations. Any preflight failure terminates immediately with structured remediation.
  6. Deterministic exit. Stop on phase_complete or spec_complete. Escalate on all other terminal loop_signal values. Never continue on ambiguous state.
  7. Bounded execution. Hard limit of max_iterations=200. If exceeded without terminal signal, stop and escalate.

Read the full file on GitHub · 208 lines

Files

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.

Changes

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.

  1. 1mo ago First seen · 208 lines · 54 tokens per session scan A 1408a3cddf95

Subscribe to this mod's changes

foundry-implement-auto is a skill published in the GitHub repository foundry-works/foundry-mcp (4 stars, last pushed 7mo ago), licensed MIT. It adds 54 tokens to every session and 2,603 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens