setup

A project setup command that creates the configuration for automated verification and review agents. The configuration records build, lint, type-check, test, and end-to-end test commands, where end-to-end tests check complete user flows.

In plain words
What is it for?
Use it to detect project commands, create or inspect .psd/verify.json, configure test flows and strictness, and manage reviewer settings.
Why use it?
It gives the project's completion checks one shared configuration. Without that file, the verification gate and stop hook do nothing.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/psd401/psd-claude-plugins/setup
Any agent
npx skills add psd401/psd-claude-plugins --skill setup
Clone the repo
git clone --depth 1 https://github.com/psd401/psd-claude-plugins

Made for: Claude Code, Codex.

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,589 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00051 $0.01589
Opus 5 $0.00026 $0.00794
Sonnet 5 $0.00010 $0.00318
Haiku 4.5 $0.00005 $0.00159

Measured 2d ago against content hash 233031380375, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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/psd-coding-system/skills/setup/SKILL.md · 162 lines

How it starts

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

Project Setup — verification gate & reviewers

Create .psd/verify.json, the single per-project config that powers the Definition-of-Done gate (used by /lfg, the runtime-verifier agent, and the Stop hook) and the watch-until-clean loop. Without this file the gate and Stop hook are inert, so the plugin never disrupts a repo that hasn't opted in.

See docs/patterns/definition-of-done.md for the full schema.

Arguments: $ARGUMENTS

Phase 1: show / reset

CONFIG=".psd/verify.json"
case "$ARGUMENTS" in
  show)
    [ -f "$CONFIG" ] && { echo "=== $CONFIG ==="; cat "$CONFIG"; } || echo "No $CONFIG — gate inert (run /setup to create)."
    exit 0 ;;
  reset)
    rm -f "$CONFIG"; echo "Removed $CONFIG. Gate is now inert for this repo."; exit 0 ;;
esac
[ -f "$CONFIG" ] && { echo "=== existing $CONFIG ==="; cat "$CONFIG"; echo; }

Phase 2: Auto-detect commands

Detect the project's real commands before asking — propose, don't interrogate.

echo "=== detecting project commands ==="
if [ -f package.json ]; then
  for s in build lint typecheck test; do
    jq -e ".scripts.\"$s\"" package.json >/dev/null 2>&1 && echo "  $s → npm run $s"
  done
  jq -e '.devDependencies["@playwright/test"] // .dependencies["@playwright/test"]' package.json >/dev/null 2>&1 && echo "  e2e → npx playwright test"
fi
[ -f pyproject.toml ] || [ -f pytest.ini ] && echo "  test → pytest ; lint → ruff check ."
[ -f Cargo.toml ] && echo "  test → cargo test ; lint → cargo clippy -- -D warnings"
[ -f go.mod ] && echo "  test → go test ./... ; lint → go vet ./..."

Lint must be zero-warning — propose the warnings-as-errors form (eslint --max-warnings 0, ruff check, clippy -- -D warnings).

Phase 3: Auto-detect the AI reviewers

The watch-until-clean loop must know which reviewer logins to wait for. Detect them from recent PRs:

echo "=== recent PR reviewers (bots + humans) ==="
DEF=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name' 2>/dev/null || echo main)
for pr in $(gh pr list --state all --limit 10 --json number --jq '.[].number' 2>/dev/null); do
  gh api "repos/{owner}/{repo}/pulls/$pr/reviews" --jq '.[].user.login' 2>/dev/null
done | sort -u

Read the full file on GitHub · 162 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 First seen · 162 lines · 51 tokens per session scan A 233031380375

Subscribe to this mod's changes

setup is a skill published in the GitHub repository psd401/psd-claude-plugins (2 stars, last pushed 9d ago), licensed MIT. It adds 51 tokens to every session and 1,589 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.

Related

Other skills, from other repositories

use-agent-browser-for-airi

Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…

moeru-ai/airi · 87 tokens

test-conversion

Workflow for converting unit tests to browser tests for Project Bedrock. Invoke this when the user wants to remove complex Browser dependencies from tests.

chromium/chromium · 31 tokens

agui-dotnet-cross-language-tests

Author cross-language interop tests that verify the AG-UI .NET SDK is wire-compatible with the TypeScript SDK — a Vitest TS client driving a C# CrossLanguage.TestServer over HTTP, both directions, including protobuf byte-parity against @ag-ui/proto. USE FOR: adding or modifying cross-language interop coverage…

ag-ui-protocol/ag-ui · 146 tokens

cli-e2e-testcase-writer

Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.

larksuite/cli · 78 tokens

harness-test-writer

Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…

maximhq/bifrost · 133 tokens

launch

Launch Code OSS (VS Code from sources) into an isolated throwaway profile with unique debug ports so you can drive it with @playwright/cli AND attach a Node debugger via dap-cli in the same session. Use when working on VS Code itself and you want to interact with the running workbench, automate chat or UI flows, test…

microsoft/vscode · 96 tokens