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 project-onboardinggit 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/project-onboarding)<a href="https://agentmods.dev/skills/bechsteindigital/claude-shiploop/project-onboarding"><img src="https://agentmods.dev/badge/skills/bechsteindigital/claude-shiploop/project-onboarding/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/project-onboarding"><img src="https://agentmods.dev/badge/skills/bechsteindigital/claude-shiploop/project-onboarding.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.00057 | $0.00695 |
| Opus 5 | $0.00028 | $0.00347 |
| Sonnet 5 | $0.00011 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
project-onboarding 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 10d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Onboarding (Pitch Interview)
Goal
Extract all information from a pitch until autonomous work is possible — captured as an approved
project/BRIEF.md. This is the last opportunity to ask the user questions;
afterwards autonomous-setup takes over without follow-ups.
Process
1. Mirror the pitch
Reflect the idea back in 2–3 of your own sentences (core idea, assumed user, assumed problem). Only start the interview once the user has confirmed or corrected the reflection.
2. Interview in rounds
Ask questions with AskUserQuestion (max. 4 per round), one topic block per round,
rounds build on each other. Question catalog: references/interview-guide.md — adapt
round and wording to the answers there; don't work through it mechanically.
Order: A Core (problem, user, success) → B Scope (must-have outcomes, non-goals, smallest shippable version) → C Frame (time, cost, tech constraints, platform) → D Autonomy (escalation rules, extension budget, deployment limits).
Rules:
- After each round, briefly summarize what is now settled.
- "Don't know" → propose a default yourself and only have it confirmed — never drill deeper.
- Technical detail questions only if the user is visibly technical; otherwise ask about effect, not technology.
- No leading questions that grow the scope ("Wouldn't you also like …?"). The interview exists to sharpen the core, not to collect features.
- Spontaneous feature ideas — whether from the user ("Oh, and X would be cool too!") or the interviewer:
acknowledge briefly, note as a candidate for
project/IDEAS.mdand possibly as a non-goal, don't go deeper, return to the core. Only if the user insists it belongs to the core is it treated as a must-have-outcome candidate.
3. Check the Definition of Ready
Checklist in references/interview-guide.md#definition-of-ready. Every open item → a targeted
follow-up round or a marked default. Don't start while any item is neither answered nor
covered by a confirmed default.
What ships with it
1 file 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.
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.
- 10d ago First seen · 59 lines · 57 tokens per session scan A 7222449fdf50
project-onboarding is a skill published in the GitHub repository BechsteinDigital/claude-shiploop (4 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 695 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.
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
Orchestrate large, multi-stage engineering work with a decision-focused Lead, reusable economy Workers, repository-backed handoffs, and optional host task messaging. Activate only for an explicit $tao command. Do not orchestrate simple local edits or activate merely because this skill is being maintained.
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.
config-validator
Validate AIWG configuration files and project setup for correctness and completeness.
summarize-transcript
Analyze and summarize a transcript, meeting notes, or discussion thread into a clear actionable document.