What is autonomous-setup?

A setup workflow for a project whose product brief has already been approved. It researches options, records technical decisions, creates the initial structure, and prepares a task backlog without asking follow-up questions.

Use it to research alternatives, choose a technology approach, scaffold a project, and organize its first implementation tasks.

It removes repeated decision prompts after the project’s goals and constraints have been approved, while recording open choices as decision notes.

autonomous-setup — Skill for Claude Code by BechsteinDigital

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 BechsteinDigital/claude-shiploop --skill autonomous-setup

Clone the repo

git clone --depth 1 https://github.com/BechsteinDigital/claude-shiploop

Made for: Claude Code.

Or install claude-shiploop, the plugin that ships this one along with the rest of its 8 skills.

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/bechsteindigital/claude-shiploop/autonomous-setup/github.svg)](https://agentmods.dev/skills/bechsteindigital/claude-shiploop/autonomous-setup)

Your own site

<a href="https://agentmods.dev/skills/bechsteindigital/claude-shiploop/autonomous-setup"><img src="https://agentmods.dev/badge/skills/bechsteindigital/claude-shiploop/autonomous-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bechsteindigital/claude-shiploop/autonomous-setup"><img src="https://agentmods.dev/badge/skills/bechsteindigital/claude-shiploop/autonomous-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 759 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.00061	$0.00759
Opus 5	$0.00030	$0.00380
Sonnet 5	$0.00012	$0.00152
Haiku 4.5	$0.00006	$0.00076

Measured 9d ago against content hash 7b3f6dcbe5bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

autonomous-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 9d 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.

autonomous-setup/SKILL.md · 60 lines

How it starts

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

Autonomous Setup

Principle

From here on, no questions to the user. Every open decision is made autonomously and logged in project/DECISIONS.md as an ADR. Only exceptions: the escalation criteria from the autonomy contract in project/BRIEF.md.

No AskUserQuestion tool (enforced): a reversible open decision → decide and log an ADR; an escalation criterion hit → stop with a decision memo. Never an interactive prompt.

Precondition

project/BRIEF.md exists with status APPROVED. Otherwise abort and request project-onboarding.

Phases

1. Research (timeboxed, parallel)

First read the global knowledge base (resolve: $SKILLS_KNOWLEDGE_DIR if set, otherwise the path in <skills-dir>/_shared/knowledge.path — written by install.sh; if neither resolves → skip) — documented learnings from earlier projects replace research and prevent repeat mistakes.

Then parallel read-only subagents in one invocation block, one per question:

Alternatives: What already exists? What does it not do well enough? (confirms/sharpens the core contract)
Tech options: 2–3 stack candidates fitting the must-have outcomes, target environment, and cost frame — with trade-offs, not with a winner
Risks: legal, technical, and cost traps of the domain

Results go to project/log/<date>-research-<topic>.md. Research findings that suggest new features go into project/IDEAS.md — never directly into scope.

2. Decide

Determine stack, architecture cut, and project structure: one ADR each in project/DECISIONS.md (decision, alternatives, rationale, reversal cost). On a tie, the decider is: least complexity for the must-have outcomes — not the most interesting technology.

3. Scaffold

Initialize the repo (if not present), skeleton per the ADRs, .gitignore, minimal README.
Create project/PROFILE.md from _shared/templates/PROFILE.template.md. Enter each command (build, test, lint, run) only after it ran successfully once.
A walking skeleton is enough: buildable, testable, startable. No feature implementation during setup.

Read the full file on GitHub · 60 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.

9d ago First seen · 60 lines · 61 tokens per session scan A 7b3f6dcbe5bc

Subscribe to this mod's changes

autonomous-setup is a skill published in the GitHub repository BechsteinDigital/claude-shiploop (4 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 759 once invoked, about $0.0003 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-31.

Autonomous Agents Claude Code Multi-Agent Planning agent-orchestration ai-agents claude-skills

fable-commander

A planning and review workflow in which one model prepares decisions while selected models handle research and execution. It is written for Fable and Claude Code, tools for coordinating multi-step software work.

DennisWei9898/fable-commander · 176 tokens

tao

Orchestrate large, multi-stage, or long-running engineering work with a persistent strong Project Lead, reusable economy Workers, optional review, and repository-backed handoffs. Activate only for an explicit $tao command; existing state or work on TAO itself never activates it implicitly. Do not start the full…

jaywavfeng/tiered-agent-orchestrator · 80 tokens

autonomous-setup