claude-pilot: Skill for Claude Code

.claude/skills/setup-workflow/SKILL.md

setup-workflow is a skill for Claude Code from changoo89/claude-pilot. It costs 28 tokens per session (1,733 once invoked), scanned A, original, MIT.

A first-time setup workflow for the claude-pilot plugin that creates project folders, configures a status display, syncs documentation, and requests a GitHub star.

In plain words
What is it for?
Use it when starting claude-pilot in a new project or resetting its project directory structure.
Why use it?
It gathers the plugin’s project files and settings in one setup process instead of requiring separate manual steps.

Skill for Claude Code

Written for Claude Code: $CLAUDE_PROJECT_DIR variable. Also seen: reads .claude/ paths; mentions .claude-plugin; mentions CLAUDE.md.

This is changoo89/claude-pilot's own configuration. It tells Claude Code how to work on claude-pilot itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-pilot configures →

Part of the claude-pilot plugin — 32 skills, 11 commands, 14 agents, 2 MCP servers shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to changoo89/claude-pilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/changoo89/claude-pilot/main/.claude/skills/setup-workflow/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/changoo89/claude-pilot

Made for: Claude Code.

Or install claude-pilot, the plugin that ships this one along with the rest of its 32 skills, 11 commands, 14 agents, 2 MCP servers.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/changoo89/claude-pilot/setup-workflow/github.svg)](https://agentmods.dev/skills/changoo89/claude-pilot/setup-workflow)
Your own site
<a href="https://agentmods.dev/skills/changoo89/claude-pilot/setup-workflow"><img src="https://agentmods.dev/badge/skills/changoo89/claude-pilot/setup-workflow/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 setup-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/changoo89/claude-pilot/setup-workflow"><img src="https://agentmods.dev/badge/skills/changoo89/claude-pilot/setup-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,733 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.01733
Opus 5.5 $0.00011 $0.00693
Sonnet 5.5 $0.00006 $0.00347
Haiku 4.5 $0.00003 $0.00173

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

Security

Grade A, and why

setup-workflow 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 2mo 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.

.claude/skills/setup-workflow/SKILL.md · 230 lines

How it starts

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

SKILL: Setup (Plugin Initialization Workflow)

Purpose: Initialize claude-pilot plugin for new projects with proper directory structure and configuration Target: User running /pilot:setup for first time in a project


Quick Start

When to Use This Skill

  • First-time plugin setup in a new project
  • Reset plugin directory structure
  • Configure statusline for project

Quick Reference

# Full workflow
/pilot:setup

# Steps: Directories → Statusline → Documentation → GitHub Star

Execution Steps

Execute ALL steps in sequence. Do NOT pause between steps unless explicitly marked as user interaction.

Step 1: Create Directories

Purpose: Initialize .pilot directory structure for plan management

mkdir -p .pilot/plan/{draft,pending,in_progress,done}
mkdir -p .pilot/state

echo "✓ .pilot directories created"

Verification:

test -d .pilot/plan/draft && echo "draft: ✓" || echo "draft: ✗"
test -d .pilot/plan/pending && echo "pending: ✓" || echo "pending: ✗"
test -d .pilot/plan/in_progress && echo "in_progress: ✓" || echo "in_progress: ✗"
test -d .pilot/plan/done && echo "done: ✓" || echo "done: ✗"
test -d .pilot/state && echo "state: ✓" || echo "state: ✗"

Step 2: Configure Statusline

Purpose: Copy statusline script from plugin and configure settings.json

# Detect plugin installation path
PLUGIN_PATH=$(jq -r '.plugins["claude-pilot@claude-pilot"][0].installPath // empty' ~/.claude/plugins/installed_plugins.json 2>/dev/null || true)
SOURCE=""

# Always prefer plugin version to ensure latest
# Note: In distributed plugin, scripts are at $PLUGIN_PATH/scripts/ (no .claude prefix)
[[ -n "$PLUGIN_PATH" && -f "$PLUGIN_PATH/scripts/statusline.sh" ]] && SOURCE="$PLUGIN_PATH/scripts/statusline.sh"

if [[ -n "$SOURCE" ]]; then
    # Copy statusline script
    mkdir -p .claude/scripts
    cp "$SOURCE" .claude/scripts/statusline.sh
    chmod +x .claude/scripts/statusline.sh

    # Configure settings.json
    SETTINGS=".claude/settings.json"
    STATUSLINE='{"type":"command","command":"\"$CLAUDE_PROJECT_DIR\"/.claude/scripts/statusline.sh"}'

    if [[ -f "$SETTINGS" ]]; then
        # Update existing settings
        jq --argjson sl "$STATUSLINE" '. + {statusLine: $sl}' "$SETTINGS" > /tmp/settings.json && mv /tmp/settings.json "$SETTINGS"
    else
        # Create new settings
        echo "{\"statusLine\": $STATUSLINE}" > "$SETTINGS"
    fi

    # Show version
    PLUGIN_VERSION=$(jq -r '.version' "$PLUGIN_PATH/.claude-plugin/plugin.json" 2>/dev/null || echo 'unknown')
    echo "✓ Statusline configured (from plugin v$PLUGIN_VERSION)"
else
    echo "⚠ Statusline script not found in plugin, skipping"
fi

Read the full file on GitHub · 230 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. 2mo ago First seen · 230 lines · 28 tokens per session scan A e67da2ae190d

Subscribe to this mod's changes

setup-workflow is a skill published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 8mo ago), licensed MIT. It adds 28 tokens to every session and 1,733 once invoked, about $0.0001 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

skill-factory

A workflow that examines completed session work and turns reusable patterns into Claude Code skills.

sangrokjung/claude-forge · 122 tokens

session-wrap

Use when wrapping up a session before ending. 4 parallel subagents detect doc updates, repeated patterns, learning points, and follow-ups, then a verifier deduplicates and presents choices. Triggers on /session-wrap, session wrap, session cleanup, end of session.

sangrokjung/claude-forge · 58 tokens

low-code-platforms

Low-code and internal tool platforms including Retool, Supabase, Appsmith, Tooljet, n8n, and Zapier. Use when building admin panels, internal tools, workflow automations, or integrating low-code platforms with custom code.

travisjneuman/.claude · 54 tokens

relay

Session relay — compresses what's been done so far (writes a one-liner for /compact) and generates a "next task" prompt (a baton) for the user to hand off. Use on requests like "relay / hand off / next session / continue after compact / baton / handoff / clean up context and continue next task." Does not run /compact…

sangrokjung/claude-forge · 97 tokens

strategic-compact

Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

sangrokjung/claude-forge · 27 tokens

agent-teams

Multi-agent team orchestration with native Agent Teams. Trigger when the user wants to launch a team of agents, coordinate parallel work with inter-agent communication, or use swarm mode.

christopherlouet/claude-base · 39 tokens