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.
/plugin marketplace add Raven-Scout/scout-plugin/plugin install scoutWrote 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/commands/raven-scout/scout-plugin/scout-update)<a href="https://agentmods.dev/commands/raven-scout/scout-plugin/scout-update"><img src="https://agentmods.dev/badge/commands/raven-scout/scout-plugin/scout-update.svg" alt="Measured on agentmods" 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.00040 | $0.02309 |
| Opus 5 | $0.00020 | $0.01154 |
| Sonnet 5 | $0.00008 | $0.00462 |
| Haiku 4.5 | $0.00004 | $0.00231 |
Grade A, and why
scout-update 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 6d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scout Update
You are the Scout updater. This command upgrades an existing vault against the current plugin templates without clobbering vault customizations. It runs an 8-stage pipeline (pre-flight → migrations → cat-1 file overwrites → cat-1b runner regeneration → cat-4 3-way merge → job lifecycle → version stamp → doctor).
This command is for existing vaults only. If no vault exists, refuse and tell the user to run /scout-setup.
Locating scoutctl — canonical resolver
Every shell block in this command runs in a fresh process, so variables set in one block do not carry into the next. Each block that needs the plugin root must re-resolve it at its top using the canonical resolver snippet below.
Canonical resolver (copy verbatim into every block that needs $NEW_ROOT / $SCOUTCTL):
NEW_ROOT="$HOME/scout-plugin"
[ -d "$NEW_ROOT/.git" ] || NEW_ROOT="$(claude plugin list --json 2>/dev/null \
| python3 -c "import sys,json;print(next(p['installPath'] for m in json.load(sys.stdin).get('plugins',{}).values() for p in m if 'scout-plugin' in p['installPath']))" 2>/dev/null)"
SCOUTCTL="$NEW_ROOT/.venv/bin/scoutctl"
This prefers the maintainer git checkout (~/scout-plugin when a .git dir is present) and otherwise falls back to the freshly-installed marketplace cache path. Do NOT use ${CLAUDE_PLUGIN_ROOT:-$HOME/scout-plugin} in any block — after Step 0.5 refreshes the plugin, $CLAUDE_PLUGIN_ROOT may still point at the pre-refresh path.
Use "$SCOUTCTL" in every subsequent invocation.
Step 0.5: Refresh the plugin (Surface A) before upgrading the vault (Surface B)
This command updates both surfaces — the plugin first, then the vault against the freshly-refreshed plugin. That order matters: upgrading the vault against a stale plugin would apply old templates and miss engine fixes that landed since the last claude plugin install.
Pull the latest plugin code:
bash <<'EOF'
set -e
if [ -d "$HOME/scout-plugin/.git" ]; then
git -C "$HOME/scout-plugin" pull --ff-only && echo "PULLED_DIRECTORY:$HOME/scout-plugin"
else
claude plugin marketplace update scout-plugin || true
claude plugin install scout@scout-plugin || true
echo "REFRESHED_MARKETPLACE"
fi
EOF
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.
- 6d ago First seen · 189 lines · 40 tokens per session scan A 494187051dbe
scout-update is a command published in the GitHub repository Raven-Scout/scout-plugin (15 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 2,309 once invoked, about $0.0002 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-30.
Other commands, from other repositories
orbit-run
Run a task through the Orbit loop (read→plan→act→evaluate→update→decide) instead of free-editing.
research
Deep research on Claude models — full multi-agent loop, plan-only, or resume a run. Persists cited evidence to runs/ /.
ccc-orchestrate
Sequential and tmux/worktree orchestration guidance for multi-agent workflows.
statusline
Show the governor fleet in your Claude Code statusline. Explicit, opt-in, and chains — it never replaces an existing statusline.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
complete
Signal that a skill's work is complete. Triggers downstream subscriptions with "when": "complete" timing. Automatically invoked — do not run manually.