do-setup

do-setup is a skill for Claude Code, Codex from fabio-barboza/development-orchestrator. It costs 125 tokens per session (5,070 once invoked), scanned A, original, MIT.

A project-initialization procedure that examines a codebase, identifies relevant skills, and writes project guidance into a supported configuration file such as CLAUDE.md or .cursorrules.

In plain words
What is it for?
It is for setting up an agent-assisted development project and creating or updating its configuration document. It does not run the application, tests, builds, or servers.
Why use it?
It gives the coding agent a summary of the project, its conventions, and available skills without requiring you to prepare that information manually.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

Good fit It is for setting up an agent-assisted development project and creating or updating its configuration document. It does not run the application, tests, builds, or servers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fabio-barboza/development-orchestrator/do-setup
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 fabio-barboza/development-orchestrator --skill do-setup
Clone the repo
git clone --depth 1 https://github.com/fabio-barboza/development-orchestrator

Made for: Claude Code, Codex.

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 do-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/fabio-barboza/development-orchestrator/do-setup/github.svg)](https://agentmods.dev/skills/fabio-barboza/development-orchestrator/do-setup)
Your own site
<a href="https://agentmods.dev/skills/fabio-barboza/development-orchestrator/do-setup"><img src="https://agentmods.dev/badge/skills/fabio-barboza/development-orchestrator/do-setup/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 do-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/fabio-barboza/development-orchestrator/do-setup"><img src="https://agentmods.dev/badge/skills/fabio-barboza/development-orchestrator/do-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 125 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,070 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 6 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Tool Misuse · line 184
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • high Tool Misuse · line 191
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • high Tool Misuse · line 198
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • high Tool Misuse · line 205
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • medium Excessive Agency · line 12
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium MCP Rug Pull · line 176
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
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.00125 $0.05070
Opus 5.5 $0.00050 $0.02028
Sonnet 5.5 $0.00025 $0.01014
Haiku 4.5 $0.00013 $0.00507

Measured 18d ago against content hash cbffbc3ef862, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

do-setup 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 18d 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/do-setup/SKILL.md · 244 lines

How it starts

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

Project Setup

Role

You are a senior developer advocate responsible for project initialization, tooling configuration, and ensuring the agent-assisted development environment is correctly set up.

Autonomous Execution Policy

CRITICAL: NEVER pause, stop, or wait for user input during execution. Proceed through ALL steps autonomously without asking the user to "continue", "proceed", or confirm intermediate results. The ONLY acceptable reasons to stop and ask the user are:

  1. The mandatory initial AI tool selection question (Step 0). This is the FIRST action the skill performs and is always required.
  2. When there is a genuine doubt or ambiguity that cannot be resolved by reading the project files.

Execution Constraints

CRITICAL: This skill MUST NOT execute the application, run tests, start servers, compile code, or perform any runtime validation. Its sole purpose is to analyze the project structure and produce the configuration document. All analysis must be done by reading files and inspecting the directory structure — never by running the application.

Procedures

Preamble: Parse Invocation Argument Check if the user invoked this skill with the argument agents (e.g., /do-setup agents).

  • If the argument is agents: set mode = agents-only. Skip Steps 1–4 and 6. Execute only Step 0 (AI tool selection) and Step 5 (install agents).
  • If no argument or any other argument: set mode = full. Execute all steps in order.

Step 0: Ask the User Which AI Tool to Configure (MANDATORY FIRST ACTION — HARD STOP)

⛔ HARD STOP — DO NOT SKIP THIS QUESTION UNDER ANY CIRCUMSTANCE.

This question is the very first action of the skill. It is MANDATORY even when:

  • you (the model) are running inside OpenCode, Claude Code, Cursor, or GitHub Copilot — the host you are running in is IRRELEVANT to the answer; the user may want to configure THIS project for a DIFFERENT tool;
  • the project already contains .claude/, .opencode/, AGENTS.md, .cursor/, .github/, opencode.json, CLAUDE.md, or any other tool-specific file or directory — these signals are forbidden inputs for this decision;
  • the user appears to have a "default" tool from prior conversations or memory — ignore it; ask again every time.

❌ DO NOT auto-detect, infer, guess, default, pre-fill, or assume the answer. ❌ DO NOT announce the answer and ask for confirmation ("I'll assume Opencode — ok?"). That is still skipping the question. ❌ DO NOT read any project file or run any directory listing before asking. ✅ DO stop execution right now and ask the user the question below verbatim.

Read the full file on GitHub · 244 lines

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. 18d ago Changed · +7 lines cbffbc3ef862
  2. 1mo ago First seen · 237 lines · 125 tokens per session scan A c4300df3a978

Subscribe to this mod's changes

do-setup is a skill published in the GitHub repository fabio-barboza/development-orchestrator (30 stars, last pushed 17d ago), licensed MIT. It adds 125 tokens to every session and 5,070 once invoked, about $0.0005 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-30.

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

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

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens