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/fabio-barboza/development-orchestrator/do-setupnpx skills add fabio-barboza/development-orchestrator --skill do-setupgit clone --depth 1 https://github.com/fabio-barboza/development-orchestratorWrote 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/fabio-barboza/development-orchestrator/do-setup)<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="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.00125 | $0.04664 |
| Opus 5 | $0.00063 | $0.02332 |
| Sonnet 5 | $0.00025 | $0.00933 |
| Haiku 4.5 | $0.00013 | $0.00466 |
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 5d 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 — 237 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:
- The mandatory initial AI tool selection question (Step 0). This is the FIRST action the skill performs and is always required.
- 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.
What ships with it
18 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.
- agents/claude/agents/agent-execute-task.md 4.0 KB
- agents/claude/commands/do-execute-all-tasks.md 12 KB
- agents/cursor/agents/agent-execute-task.md 4.0 KB
- agents/cursor/commands/do-execute-all-tasks.md 11 KB
- agents/github/agents/agent-execute-task.agent.md 4.4 KB
- agents/github/prompts/do-execute-all-tasks.prompt.md 11 KB
- agents/opencode/agents/agent-execute-task.md 4.2 KB
- agents/opencode/commands/do-create-prd.md 572 B
- agents/opencode/commands/do-create-tasks.md 594 B
- agents/opencode/commands/do-create-techspec.md 532 B
- agents/opencode/commands/do-execute-all-tasks.md 11 KB
- agents/opencode/commands/do-execute-qa-bugfix.md 718 B
- agents/opencode/commands/do-execute-qa.md 622 B
- agents/opencode/commands/do-execute-review-fix.md 736 B
- agents/opencode/commands/do-execute-review.md 638 B
- agents/opencode/commands/do-execute-task.md 643 B
- agents/opencode/commands/do-setup.md 633 B
- agents/opencode/commands/do-status.md 515 B
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.
- 5d ago First seen · 237 lines · 125 tokens per session scan A c4300df3a978
do-setup is a skill published in the GitHub repository fabio-barboza/development-orchestrator (28 stars, last pushed 5d ago), licensed MIT. It adds 125 tokens to every session and 4,664 once invoked, about $0.0006 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.
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…