meta-setup

meta-setup is a skill for Claude Code, Codex from volomydyr/design-engineer-plugin. It costs 55 tokens per session (4,748 once invoked), scanned B, original, MIT.

A setup assistant for a design-engineering project. It checks the project’s current situation and guides new projects through setup, returning projects through unfinished work, or existing projects through available capabilities.

In plain words
What is it for?
Use it as the first command in a design-engineering project to start setup, resume a previous workflow, or see what the project can do.
Why use it?
It gives the developer the right starting workflow instead of making them guess which setup or continuation steps apply. It also requires explicit choices when user decisions are needed.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the design-engineer plugin — 35 skills, 11 commands, 10 agents, 6 hooks shipped together

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.

agentmods
npx agentmods add skills/volomydyr/design-engineer-plugin/meta-setup
Any agent
npx skills add volomydyr/design-engineer-plugin --skill meta-setup
Clone the repo
git clone --depth 1 https://github.com/volomydyr/design-engineer-plugin

Made for: Claude Code, Codex.

Or install design-engineer, the plugin that ships this one along with the rest of its 35 skills, 11 commands, 10 agents, 6 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.

agentmods badge for meta-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/volomydyr/design-engineer-plugin/meta-setup.svg)](https://agentmods.dev/skills/volomydyr/design-engineer-plugin/meta-setup)
Your own site
<a href="https://agentmods.dev/skills/volomydyr/design-engineer-plugin/meta-setup"><img src="https://agentmods.dev/badge/skills/volomydyr/design-engineer-plugin/meta-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,748 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
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 $0.00055 $0.04748
Opus 5 $0.00028 $0.02374
Sonnet 5 $0.00011 $0.00950
Haiku 4.5 $0.00006 $0.00475

Measured 4d ago against content hash 81175c9aa596, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

meta-setup scanned grade B with 1 finding 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.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/detect-environment.sh, scripts/detect-state.sh, scripts/init-project-structure.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

**First**, detect prior installation: read `~/.claude/settings.json` (if it exists) and check if `statusLine.command` references `de-statusline.js`. If yes, present the 3-option question; if no, present the 2-option ques
skills/meta-setup/SKILL.md · 372 lines

How it starts

The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design-Engineer Plugin Setup

Interaction Method

If AskUserQuestion is available, use it for all prompts below.

If not, present each question as a numbered list and wait for a reply before proceeding to the next step. For multiSelect questions, accept comma-separated numbers (e.g. 1, 3). Never skip or auto-configure without explicit user consent.


Step 1: Read Config

Read .design-engineer-plugin/config.yaml. Check the project_type field:

  • If project_type: existing → this is an existing project, NOT a returning pipeline project. The hook injects context for this case. Follow the hook's instructions (show capabilities via AskUserQuestion). Do NOT show pipeline state or resume information.
  • If project_type: new → this is a returning pipeline project. Continue with Path A below.

Do not mention config files, detection state, or project types to the user. No jargon.

Path A: Returning Pipeline Project (project_type: new only)

If the state is returning_with_resume, read the config file and show the current state in plain language:

Welcome back. Here's where you are:

You're in the {phase_name} phase.
Last thing completed: {human-readable deliverable name, not the internal skill ID}
Up next: {human-readable name}
{count} deliverables created, {stale_count} may need a look.

Then ask:

question: "What would you like to do?"
header: "Resume"
options:
  - label: "Pick up where I stopped"
    description: "Continue with {human-readable next step name}"
  - label: "Work on a different phase"
    description: "Jump to discovery, strategy, planning, or design"
  - label: "See what else I can do"
    description: "Browse all available commands and capabilities"
  - label: "Start over"
    description: "Reset the plugin setup for this project"

If "Continue" or "Jump": suggest running /design-engineer:discovery to resume the pipeline. If "Browse": show the full capability list inline (see below), then suggest relevant /design-engineer: commands. If "Reconfigure": proceed to Step 2.

Read the full file on GitHub · 372 lines

Files

What ships with it

6 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. 4d ago First seen · 372 lines · 55 tokens per session scan B 81175c9aa596

Subscribe to this mod's changes

meta-setup is a skill published in the GitHub repository volomydyr/design-engineer-plugin (19 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 4,748 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 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