setup-config

setup-config is a skill for Claude Code from Sassy-Dog/sassydog-skills. It costs 199 tokens per session (4,095 once invoked), scanned A, original, Apache-2.0.

A configuration generator for a repository's workflow skills. It writes repository-specific settings files for tasks such as reviewing work, grooming a backlog, sending changes, and tidying the repository.

In plain words
What is it for?
Use it to set up or refresh the repository's workflow configuration, verify configured facts, and migrate older configuration layouts.
Why use it?
It keeps workflow instructions tailored to the repository while avoiding settings that can be discovered automatically or become outdated.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions subagents.

Part of the sassy-dog plugin — 21 skills, 10 agents shipped together

Good fit Use it to set up or refresh the repository's workflow configuration, verify configured facts, and migrate older configuration layouts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sassy-dog/sassydog-skills/setup-config
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 Sassy-Dog/sassydog-skills --skill setup-config
Clone the repo
git clone --depth 1 https://github.com/Sassy-Dog/sassydog-skills

Made for: Claude Code.

Or install sassy-dog, the plugin that ships this one along with the rest of its 21 skills, 10 agents.

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-config

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/sassy-dog/sassydog-skills/setup-config"><img src="https://agentmods.dev/badge/skills/sassy-dog/sassydog-skills/setup-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 199 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,095 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.00199 $0.04095
Opus 5 $0.00100 $0.02048
Sonnet 5 $0.00040 $0.00819
Haiku 4.5 $0.00020 $0.00409

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

Security

Grade A, and why

setup-config 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 2d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/detect-capabilities.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/setup-config/SKILL.md · 284 lines

How it starts

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

Setup Config

Configuration generator for the workflow family. The six skills themselves — survey-work, groom-backlog, take-it, dispatch-ready, send-it, tidy-repo — ship generically in this plugin. This skill writes the per-repo config they read:

.claude/sassy-dog/<skill>.md      # YAML frontmatter (facts) + ## sections (prose)
.claude/settings.json             # extraKnownMarketplaces + enabledPlugins declarations

The format is references/config-contract.md. Read it before writing anything.

This skill does not render skill bodies. A repo that still has .claude/skills/{plate-it,fill-it,take-it,drain-it,send-it,clean-it}/ is on the superseded architecture and needs migrate mode (Phase 3).

Two rules that shape everything here

Configure only what cannot be derived. Repo slug, default branch, and delete_branch_on_merge come from gh repo view at runtime and never appear in config. A configured value is a value that can drift — see the drift incident recorded in references/config-contract.md.

Re-verify every configured fact against live state. Never copy a fact forward from an existing render or config just because it is written down. merge_queue in particular has no gh repo view equivalent and must be read from GraphQL:

gh api graphql -f query='{repository(owner:"OWNER",name:"NAME"){mergeQueue(branch:"BRANCH"){id}}}' \
  --jq '.data.repository.mergeQueue != null'

Phase 0 — locate and pick the mode

Confirm cwd is a git repo with a GitHub remote:

gh repo view --json nameWithOwner,defaultBranchRef,deleteBranchOnMerge,visibility

visibility is on that call for one reason and is read exactly once: it seeds review_site: (Phase 1). Extend this call rather than adding a second one — and never re-read it on a refresh, for the reason Phase 4 gives.

Probe the remote before trusting the checkout. Every signal the mode table reads lives in the working tree, and the working tree can be days stale. Fetch, then list what the remote default branch actually carries (BRANCH is defaultBranchRef from the probe above — never assume main):

Read the full file on GitHub · 284 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. 2d ago Changed · +15 lines ee3b4b1fcd4d
  2. 4d ago Changed · +14 lines 2e528275c55e
  3. 11d ago First seen · 255 lines · 199 tokens per session scan A ba98a52d656d

Subscribe to this mod's changes

setup-config is a skill published in the GitHub repository Sassy-Dog/sassydog-skills (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 199 tokens to every session and 4,095 once invoked, about $0.0010 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.

Related

Other skills, from other repositories

create-site

Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…

microsoft/power-platform-skills · 73 tokens

google-ads-audit

Google Ads account audit and business context setup. Use for account-health audits and business-context setup. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should I fix in my ads", or when the user is new to NotFair and hasn't run…

nowork-studio/notfair-plugin · 86 tokens

review

5-pass structured code review — correctness, security, performance, readability, consistency.

SethGammon/Citadel · 17 tokens

alive:system-upgrade

Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.

alivecontext/alive · 57 tokens

extract-resume

Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.

suxrobGM/jobpilot · 32 tokens

ensure-pipelines-host

Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host…

microsoft/power-platform-skills · 222 tokens