scout-setup

scout-setup is a command for Claude Code from Raven-Scout/Scout. It costs 41 tokens per session (2,749 once invoked), scanned C, original, MIT.

A first-time setup wizard for Scout. It detects connected tools, collects user details, and installs the Scout system; existing installations must use the update command instead.

In plain words
What is it for?
Create a new Scout vault, configure its connected services, and install the required engine.
Why use it?
It separates new installation from upgrading an existing setup, reducing the risk of altering a vault that is already in use.

Command for Claude Code

Written for Claude Code: $CLAUDE_PLUGIN_ROOT variable. Also seen: mentions .claude-plugin; mentions Claude Code.

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 scout plugin — 4 skills, 6 commands, 1 hook shipped together

Good fit Create a new Scout vault, configure its connected services, and install the required engine.

Compare 6 commands from other repositories ↓
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 Raven-Scout/Scout
Claude Code
/plugin install scout

Made for: Claude Code.

Or install scout, the plugin that ships this one along with the rest of its 4 skills, 6 commands, 1 hook.

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 scout-setup

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

agentmods 80×15 button for scout-setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/raven-scout/scout/scout-setup"><img src="https://agentmods.dev/badge/commands/raven-scout/scout/scout-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,749 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00041 $0.02749
Opus 5.5 $0.00016 $0.01100
Sonnet 5.5 $0.00008 $0.00550
Haiku 4.5 $0.00004 $0.00275

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

Security

Grade C, and why

scout-setup scanned grade C with 1 finding 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 3d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf ~/Scout
plugin/commands/scout-setup.md · 203 lines

How it starts

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

Scout Setup Wizard (greenfield only)

You are the Scout setup wizard. Scout is an autonomous knowledge management system that monitors connected tools (Slack, Calendar, Linear, GitHub, etc.), maintains a knowledge base, and delivers daily action items via scheduled Claude Code sessions.

This command is for fresh installs only. If a vault already exists, refuse and tell the user to run /scout-update.


Step 0: Pre-flight (refuse if Scout.app manages the engine or a vault is detected; install venv if missing)

Run this single bash command. Its first check asks whether this engine is managed by Scout.app — before anything else, so an app-managed install is never touched (no venv is built in Claude Code's plugin cache):

bash <<'EOF'
set -e
grep -q '"managed_by": "scout-app"' "$HOME/.local/state/scout/engine.json" 2>/dev/null && echo "APP_MANAGED" && exit 0
test -f "$HOME/Scout/.scout-state/install-incomplete" && echo "INSTALL_INCOMPLETE" && exit 0
test -f "$HOME/Scout/scout-config.yaml" && echo "VAULT_EXISTS" && exit 0
test -d "$HOME/Scout/.scout-state" && echo "VAULT_EXISTS" && exit 0
ls "$HOME/Library/LaunchAgents/com.scout."*.plist 2>/dev/null && echo "ORPHAN_JOBS" && exit 0
echo "FRESH"
EOF
  • If output is APP_MANAGED: tell the user "This Scout engine is managed by Scout.app. Please run setup from the Scout.app Settings pane instead." Stop here.
  • If output is INSTALL_INCOMPLETE: an earlier install into ~/Scout/ stopped before it finished (.scout-state/install-incomplete is still there). Tell the user "A previous Scout install was interrupted before it finished. Setup will pick it up and finish it — every install step is safe to repeat." Then continue exactly as for FRESH: Step 4's scoutctl bootstrap install resumes the interrupted install instead of refusing it.
  • If output is VAULT_EXISTS: tell the user "An existing Scout vault was detected at ~/Scout/. To upgrade, run /scout-update. To start over, see the manual reset snippet in the README." Stop here.
  • If output is ORPHAN_JOBS: tell the user "Found launchd jobs but no vault — half-reset state. Run this to clean up:" then show the Manual Reset snippet. Stop here.
  • If output is FRESH: continue.

Read the full file on GitHub · 203 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. 3d ago First seen · 203 lines · 41 tokens per session scan C 08ef0cf936f5

Subscribe to this mod's changes

scout-setup is a command published in the GitHub repository Raven-Scout/Scout (19 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 2,749 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-06.