setup

setup is a skill for Claude Code from SienkLogic/plan-build-run. It costs 22 tokens per session (2,240 once invoked), scanned A, original, MIT.

A configuration tool for an existing Plan-Build-Run project.

In plain words
What is it for?
Use it to update model profiles, workflow features, and the project's CLAUDE.md integration.
Why use it?
It lets you change project settings without restarting the project or replacing its existing planning state.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md; names the AskUserQuestion tool.

Part of the pbr plugin — 44 skills, 71 commands, 18 agents, 3 hooks shipped together

Good fit Use it to update model profiles, workflow features, and the project's CLAUDE.md integration.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sienklogic/plan-build-run/setup
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 SienkLogic/plan-build-run --skill setup
Clone the repo
git clone --depth 1 https://github.com/SienkLogic/plan-build-run

Made for: Claude Code.

Or install pbr, the plugin that ships this one along with the rest of its 44 skills, 71 commands, 18 agents, 3 hooks.

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

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

agentmods 80×15 button for setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/setup"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,240 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.00022 $0.02240
Opus 5.5 $0.00009 $0.00896
Sonnet 5.5 $0.00004 $0.00448
Haiku 4.5 $0.00002 $0.00224

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

Security

Grade A, and why

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.

plugins/pbr/skills/setup/SKILL.md · 248 lines

How it starts

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

STOP — DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes tokens. Begin executing Step 1 immediately.

Step 0 — Immediate Output

Before ANY tool calls, display this banner:

╔══════════════════════════════════════════════════════════════╗
║  PLAN-BUILD-RUN ► RECONFIGURE                                ║
╚══════════════════════════════════════════════════════════════╝

Then proceed to Step 1.

/pbr:setup — Plan-Build-Run Reconfigure

You are running the setup skill in reconfigure mode. This wizard lets existing Plan-Build-Run projects change model profiles, workflow features, and CLAUDE.md integration. It does NOT re-initialize or overwrite project state.


Step 1: Detect Project State

Check if .planning/config.json exists.

If .planning/config.json does NOT exist: Display:

No Plan-Build-Run project found in this directory.

/pbr:setup is for reconfiguring existing projects.
To start a new project, run: /pbr:new-project

/pbr:new-project includes everything /pbr:setup used to do, plus deep requirements gathering and roadmap creation.

Stop. Do not proceed further.

If .planning/config.json exists:

  • Read .planning/config.json
  • Display the current settings summary:
    Current configuration:
    - Model profile: {derived from models block — balanced/quality/budget or custom}
    - Depth: {depth}
    - Mode: {mode}
    - Auto-continue: {features.auto_continue}
    - TDD mode: {features.tdd_mode}
    - Git branching: {git.branching}
    
  • Proceed to Step 2.

Step 2: Model Selection

Note: These profiles control agent models, not the orchestrator. The orchestrator uses your Claude Code session model. For cost optimization, consider running your session on Sonnet -- agents with inherit will follow. See references/model-profiles.md for details.

Use AskUserQuestion: question: "Which model profile should agents use?" header: "Models" options: - label: "Balanced (Recommended)" description: "Sonnet for most agents, Haiku for synthesizer. Good quality/cost tradeoff." - label: "Quality" description: "Opus for executor and planner, Sonnet for others. Best results, highest cost." - label: "Budget" description: "Haiku for most agents. Fastest and cheapest, but lower quality." - label: "Keep current" description: "Leave model settings unchanged."

Read the full file on GitHub · 248 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. 1mo ago First seen · 248 lines · 22 tokens per session scan A 03bb1785b560

Subscribe to this mod's changes

setup is a skill published in the GitHub repository SienkLogic/plan-build-run (19 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 2,240 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-09-03.

Related

Other skills, from other repositories

issue-triage

3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.

FlorianBruniaux/claude-code-ultimate-guide · 81 tokens

plan-pipeline

Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.

FlorianBruniaux/claude-code-ultimate-guide · 54 tokens

routines-discover

Analyzes the current project to surface high-value Routines use cases across the three trigger types (schedule, API, GitHub events). Usage: /routines-discover.

FlorianBruniaux/claude-code-ultimate-guide · 39 tokens

notion-governance

Governance for the Clybor life-CRM Notion workspace from a build repo. Use whenever a request touches Notion — logging a decision, creating or closing a task, reading project or client state, filing a note or KB entry, or invoking any notion-search / notion-fetch / notion-create-pages / notion-update-page tool.…

shawnclybor/clybor-claude-tooling · 212 tokens

build-evaluate

Verify a completed build against the PRD's anchor case and success criteria. Runs the acceptance test and anchor-case check (serial across drivers sharing a write root), fans out 2-3 read-only cold-read agents (fresh-eyes, anti-scope-creep, drift-vs-mirror). On FAIL, auto-invokes five-whys for root-cause. On PASS with…

shawnclybor/clybor-claude-tooling · 166 tokens

meeting-workflow

Transform meeting transcripts (pasted text, .vtt/.srt/.txt uploads, or your meeting tool's export) into structured records — a summary note with decisions and open questions, plus tracked tasks for every action item. Use whenever the user pastes or uploads a meeting transcript, says "log this meeting", "process this…

shawnclybor/clybor-claude-tooling · 114 tokens