What is stitch-mcp-delete-project?

A destructive tool guide for permanently deleting a Stitch project, including all of its screens, designs, and history.

Use it only when the user explicitly asks to delete a Stitch project and has confirmed the displayed project details.

It ensures the project is identified and the user confirms before an irreversible deletion occurs.

stitch-mcp-delete-project — Skill for Claude Code by gabelul

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 gabelul/stitch-kit --skill stitch-mcp-delete-project

Clone the repo

git clone --depth 1 https://github.com/gabelul/stitch-kit

Made for: Claude Code.

Or install stitch-kit, the plugin that ships this one along with the rest of its 36 skills, 1 agent, 2 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gabelul/stitch-kit/stitch-mcp-delete-project.svg)](https://agentmods.dev/skills/gabelul/stitch-kit/stitch-mcp-delete-project)

Your own site

<a href="https://agentmods.dev/skills/gabelul/stitch-kit/stitch-mcp-delete-project"><img src="https://agentmods.dev/badge/skills/gabelul/stitch-kit/stitch-mcp-delete-project.svg" alt="Measured on agentmods" height="20"></a>

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 457 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.

Model	Per session	Once invoked
Fable 5.1	$0.00029	$0.00457
Opus 5	$0.00015	$0.00229
Sonnet 5	$0.00006	$0.00091
Haiku 4.5	$0.00003	$0.00046

Measured 8d ago against content hash 36d70ef0b998, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

stitch-mcp-delete-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 8d 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/stitch-mcp-delete-project/SKILL.md · 63 lines

What it actually says

Stitch MCP — Delete Project

Permanently deletes a Stitch project and all its screens, designs, and history. This action is irreversible.

Critical prerequisite

Only use this skill when the user explicitly mentions "Stitch".

This is a destructive action. You MUST ask the user to confirm before calling delete_project. Never auto-delete.

When to use

User explicitly asks to delete a Stitch project
Cleaning up test/scratch projects after confirming with the user
The orchestrator offers project cleanup and the user accepts

Step 1: Confirm the project

Show the user what they're about to delete:

Call stitch-mcp-get-project with projects/[ID] to get the project title and screen count
Present: "You're about to permanently delete [title] ([N] screens). This cannot be undone. Proceed?"
Only continue if the user explicitly confirms

Step 2: Call the MCP tool

{
  "name": "delete_project",
  "arguments": {
    "name": "projects/3780309359108792857"
  }
}

`name` — full path with `projects/` prefix

✅ "projects/3780309359108792857"
❌ "3780309359108792857"

This follows the same format as get_project — both use projects/ID.

After deleting

Confirm: "Project [title] has been deleted."
Offer: "Want to see your remaining projects?" → stitch-mcp-list-projects
Do NOT attempt to access the deleted project's screens or data

Anti-patterns

Never delete without explicit user confirmation — even if the orchestrator suggests cleanup
Never delete multiple projects in a batch without confirming each one
Never use numeric ID — delete_project requires the full projects/ID path

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.

8d ago First seen · 63 lines · 29 tokens per session scan A 36d70ef0b998

Subscribe to this mod's changes

stitch-mcp-delete-project is a skill published in the GitHub repository gabelul/stitch-kit (44 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 457 once invoked, about $0.0001 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-30.

Claude Code Design and UX claude-code-plugin design-to-code nextjs react-native stitch

design-to-code

Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…

yonatangross/orchestkit · 86 tokens

kit-montar

Monta um site novo combinando peças já validadas do acervo pessoal do usuário — templates, design systems, componentes, animações, menus, prompts e receitas — em vez de gerar tudo do zero. Acervo vazio: constrói do zero e oferece guardar. Recebe o briefing, decide cor e tipografia antes da identidade, pergunta que…

harebeats/cannonball · 245 tokens

kit-buscar

Consulta o acervo pessoal de sites do usuário — o que ele já guardou: templates rodáveis, design systems com paleta e tipografia, componentes de UI e de IA, animações de scroll, texto e menu, efeitos WebGL, prompts de página inteira e receitas de composição que já deram certo. Responde "o que eu já tenho pronto pra…

harebeats/cannonball · 228 tokens

kit-cor

Define a paleta do site como decisão, não como consequência de ter escolhido um design system. Faz as perguntas que determinam cor (o que a marca promete, o que o setor já usa, para onde o olho tem que ir, o que ela NÃO pode parecer), monta a paleta por papel — fundo, tinta, superfície, acento — mede o contraste de…

harebeats/cannonball · 193 tokens

kit-tipo

Define a tipografia do site como decisão — e, principalmente, resolve se dá para ENTREGAR. Confere licença (site de marca paga por tipo, e acervo montado a partir de site de marca vem cheio de fonte comercial que não se pode servir), propõe substituto livre com critério de desenho, monta o par display + corpo, gera a…

harebeats/cannonball · 199 tokens

stitch-react-native

Convert Stitch HTML designs into React Native screens, or sync existing native components to updated Stitch designs, using native primitives, StyleSheet rules, and mobile platform checks.

PracticalSwan/agent-skills · 37 tokens