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 psd401/psd-claude-plugins --skill setupgit clone --depth 1 https://github.com/psd401/psd-claude-pluginsWrote 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/psd401/psd-claude-plugins/setup)<a href="https://agentmods.dev/skills/psd401/psd-claude-plugins/setup"><img src="https://agentmods.dev/badge/skills/psd401/psd-claude-plugins/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.
<a href="https://agentmods.dev/skills/psd401/psd-claude-plugins/setup"><img src="https://agentmods.dev/badge/skills/psd401/psd-claude-plugins/setup.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.00051 | $0.01586 |
| Opus 5.5 | $0.00020 | $0.00634 |
| Sonnet 5.5 | $0.00010 | $0.00317 |
| Haiku 4.5 | $0.00005 | $0.00159 |
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 14d 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 — 161 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
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.
- 14d ago Changed · -1 lines 322a91261369
- 1mo ago Changed 6cde099f7e7c
- 2mo ago First seen · 162 lines · 51 tokens per session scan A 233031380375
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,586 once invoked, about $0.0002 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…