A setup command for configuring Claude Code with recommended tools, instructions, and project files.

Use it to initialize the credo framework and check project instructions, documentation, codebase mapping, and roadmap files.

It checks what is already configured and asks only about missing parts of the project setup.

setup — Command for Claude Code by Marcel-Bich

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 Marcel-Bich/marcel-bich-claude-marketplace

Claude Code

/plugin install credo

Made for: Claude Code.

Or install credo, the plugin that ships this one along with the rest of its 28 skills, 21 commands, 7 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/marcel-bich/marcel-bich-claude-marketplace/setup/github.svg)](https://agentmods.dev/commands/marcel-bich/marcel-bich-claude-marketplace/setup)

Your own site

<a href="https://agentmods.dev/commands/marcel-bich/marcel-bich-claude-marketplace/setup"><img src="https://agentmods.dev/badge/commands/marcel-bich/marcel-bich-claude-marketplace/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/marcel-bich/marcel-bich-claude-marketplace/setup"><img src="https://agentmods.dev/badge/commands/marcel-bich/marcel-bich-claude-marketplace/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 11,670 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 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.

Model	Per session	Once invoked
Fable 5.1	$0.00012	$0.11670
Opus 5.5	$0.00005	$0.04668
Sonnet 5.5	$0.00002	$0.02334
Haiku 4.5	$0.00001	$0.01167

Measured 13d ago against content hash 086464a1b58d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

setup scanned grade C with 2 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 13d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

| `apt` | `sudo apt update && sudo apt install -y tmux` |

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

- The limit plugin is installed: `grep -q '"limit@marcel-bich-claude-marketplace"' "$HOME/.claude/plugins/installed_plugins.json"` succeeds (same installed-plugins file the setup check reads for dogma/gsd).

plugins/credo/commands/setup.md · 962 lines

How it starts

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

Credo Setup

Set up Claude Code with the preacher's recommended tools, instructions, and project structure. credo is the core; everything else is recommended or optional and slots in around it.

Goal: Only ask about things that are NOT yet done. Skip everything already configured.

Step 1: Run Setup Check

Run the setup check script to gather all information at once:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-setup.sh"

This outputs structured results for all checks. Parse the output to determine:

plugins.dogma - Is the recommended dogma plugin installed?
plugins.gsd - Is the optional get-shit-done plugin installed?
directories.claude - Are Claude instructions present?
files.project_md - Does PROJECT.md exist? (only relevant if GSD is used)
directories.codebase_map - Is codebase mapped? (only relevant if GSD is used)
files.roadmap - Does ROADMAP.md exist? (only relevant if GSD is used)
project.state - Overall state (needs_setup, needs_mapping, needs_project, needs_roadmap, ready)
todo_tools.state / todo_tools.declined - Is the Claude Code task-list tools opt-in on for the active profile (see Step 10)?
tmux.installed / tmux.inside / tmux.platform / tmux.pkg_manager / tmux.login_shell - Is tmux installed, does this session run inside it, and how could it be installed (see Step 11)?
peer_trust_guard.quiet / peer_trust_guard.env - Does credo only remind (quiet, default) or ask for confirmation (strict) when a command grants LAN peer trust, and is the env override CREDO_PEER_TRUST_GUARD_QUIET set (see Step 12)?

If project.state = ready: Skip directly to "Setup Complete" section. Do NOT ask any questions.

Step 2: Initialize the credo Framework (Core)

This is the real first step - credo's own state tree. It is self-contained and needs no other plugin.

Run the init script (idempotent - safe to run again):

bash "${CLAUDE_PLUGIN_ROOT}/scripts/credo-init.sh"

This creates the .credo/ structure (items, process, screenshots, checklists, config, id-counter) and adds the git-exclude lines. .credo/** stays local by default. For teams that want items and process versioned in the repo, run it with CREDO_VERSION_TRACKED=1 instead (per-project config and screenshots/ stay local either way).

Read the full file on GitHub · 962 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.

13d ago Changed · +96 lines 086464a1b58d
15d ago Changed · +251 lines scan B → C 9788515fe2d7
17d ago Changed · +30 lines 27afae54bff3
1mo ago First seen · 585 lines · 12 tokens per session scan B a3365baf246a

Subscribe to this mod's changes

setup is a command published in the GitHub repository Marcel-Bich/marcel-bich-claude-marketplace (12 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 11,670 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it C with 2 findings (asks for root, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code ai-tools anthropic claude claude-ai claude-code-plugins

setup

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade C, and why

Asks for rootmediumPrivilege escalation

Reads agent configuration directoriesmediumAgent snooping

How it starts

Credo Setup

Step 1: Run Setup Check

Step 2: Initialize the credo Framework (Core)

What this file has done since we first saw it

Other commands, from other repositories

context-stats

deps-update

security-scan

test-suite

assemble-team

run