setup

setup is a command for Claude Code from pwdev-solucoes/pwdev-claude-marketplace. It costs 18 tokens per session (426 once invoked), scanned A, original, Apache-2.0.

A command that examines a project and generates a CLAUDE.md file containing its technology stack, conventions, commands, quality rules, and security guidance.

In plain words
What is it for?
Use it when starting work on a project or documenting how agents should follow its existing code and workflow conventions.
Why use it?
It gives coding agents a shared set of project-specific instructions instead of making them rediscover the same context each time.

Command for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions CLAUDE.md.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the pwdev-feat plugin — 7 commands shipped together

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add pwdev-solucoes/pwdev-claude-marketplace
Claude Code
/plugin install pwdev-feat

Made for: Claude Code.

Or install pwdev-feat, the plugin that ships this one along with the rest of its 7 commands.

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/commands/pwdev-solucoes/pwdev-claude-marketplace/setup.svg)](https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/setup)
Your own site
<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/setup"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 426 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.1 $0.00018 $0.00426
Opus 5 $0.00009 $0.00213
Sonnet 5 $0.00004 $0.00085
Haiku 4.5 $0.00002 $0.00043

Measured 2d ago against content hash 618dad5b5664, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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/pwdev-feat/commands/setup.md · 65 lines

What it actually says

/pwdev-feat:setup — Generate CLAUDE.md

Purpose

Create a CLAUDE.md file in the project root with conventions, stack info, and rules that all agents will follow.

STEP 0 — Language

Follow ${CLAUDE_PLUGIN_ROOT}/references/language.md (resolve lang from .planning/config.json; ask only if unset).

STEP 1 — Check existing

if [ -f "CLAUDE.md" ]; then
  echo "EXISTS"
  cat CLAUDE.md | head -20
else
  echo "NEW"
fi

If CLAUDE.md exists → ask: "Update existing or replace?"

STEP 2 — Gather context

# Read codebase analysis if available
cat .planning/feat/codebase.md 2>/dev/null

# Or detect fresh
cat package.json composer.json 2>/dev/null | head -30
cat .editorconfig tsconfig.json 2>/dev/null | head -20
git log --oneline -5 2>/dev/null

STEP 3 — Ask the human (1 round max)

If critical info is missing, ask:

  • What is this project? (1 sentence)
  • Any specific coding rules? (or "use defaults")

STEP 4 — Generate CLAUDE.md

Write from template in templates/CLAUDE.template.md, filling in project-specific values.

STEP 5 — Present

✅ CLAUDE.md generated

Sections: Identity, Stack, Conventions, Commands, Quality, Security, Golden Rules
Stack: {detected stack}

👉 Review CLAUDE.md and adjust as needed.
👉 Then: /pwdev-feat:feat "description" to start building.

Prohibitions

  • NEVER overwrite CLAUDE.md without asking
  • NEVER invent conventions — detect from code or ask
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 · 65 lines · 18 tokens per session scan A 618dad5b5664

Subscribe to this mod's changes

setup is a command published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 17d ago), licensed Apache-2.0. It adds 18 tokens to every session and 426 once invoked, about $0.0001 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-09-03.