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 skills add BechsteinDigital/claude-shiploop --skill autonomous-setupgit clone --depth 1 https://github.com/BechsteinDigital/claude-shiploopWrote 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/bechsteindigital/claude-shiploop/autonomous-setup)<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.
<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>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.5 | $0.00024 | $0.00304 |
| Sonnet 5.5 | $0.00012 | $0.00152 |
| Haiku 4.5 | $0.00006 | $0.00076 |
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 1mo 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 — 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.mdfrom_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.
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.
- 1mo ago First seen · 60 lines · 61 tokens per session scan A 7b3f6dcbe5bc
autonomous-setup is a skill published in the GitHub repository BechsteinDigital/claude-shiploop (4 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 759 once invoked, about $0.0002 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-31.
Other skills, from other repositories
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.
tao
Coordinate multi-stage engineering work with cost-aware Lead execution, reusable independent Workers, repository-backed handoffs, and bounded workspace housekeeping. Activate only for an explicit $tao command; maintenance of this skill never activates orchestration.
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
ramp
Fetch and follow Ramp's published agent playbooks inside Paperclip, with mandatory approval gates for spend, incorporation, cards, account setup, and other financial actions.
index-refresh
Use when an LLM Wiki operation issue requests an index refresh. Rebuild wiki/index.md from the actual wiki tree, reconcile missing/deleted entries, and log counts without editing page bodies.