agentmods.dev

scout-plan

scout-plan is a command for Claude Code from Raven-Scout/scout-plugin. It costs 56 tokens per session (3,421 once invoked), scanned A, a copy of scout-plan, MIT.

A conversation-based day planner that reviews how long earlier planned tasks took, estimates today's tasks, fits them into open calendar time, and creates Google Calendar blocks after you approve the plan.

In plain words
What is it for?
Use it to plan today, tomorrow, or a chosen date, or to record the actual time spent on past planned blocks.
Why use it?
It reduces the guesswork of deciding what fits into a day and keeps estimates grounded in your past results. It also prevents calendar changes without your explicit approval.

Command for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT variable. Also seen: 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

not rated 17repo 4d ago A scan 56 tokens copy · 100% MIT

Good fit Use it to plan today, tomorrow, or a chosen date, or to record the actual time spent on past planned blocks.

Compare 6 commands from other repositories ↓
View source ↗ Raven-Scout/scout-plugin raven-scout.github.io
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-plugin
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-plan

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/raven-scout/scout-plugin/scout-plan"><img src="https://agentmods.dev/badge/commands/raven-scout/scout-plugin/scout-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,421 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00056 $0.03421
Opus 5.5 $0.00022 $0.01368
Sonnet 5.5 $0.00011 $0.00684
Haiku 4.5 $0.00006 $0.00342

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

Security

Grade A, and why

scout-plan 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 4d 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.

Origin

This is a copy

100% identical to scout-plan — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commands/scout-plan.md · 162 lines

How it starts

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

Scout Plan

Plan the user's day in conversation: pick the tasks that need their own time, estimate each one, fit them into the free time on their calendar, and, once they say yes, put the blocks on Google Calendar and record the estimate and block on each task.

Like /scout-work, this runs in the current conversation, and the user decides. Never create, move or delete a calendar event without an explicit yes for that exact plan.

Arguments ($ARGUMENTS):

  • empty: plan today
  • tomorrow, or a date YYYY-MM-DD: plan that day
  • review: only log actual times for past blocks (Phase 1), then stop

Phase 0: Setup

  1. Vault and dates. The vault is the directory holding scout-config.yaml (the current directory, else ~/Scout). Read its timezone (default America/New_York) and compute today and the target day with TZ=<timezone> date '+%Y-%m-%d'. Tasks always live in today's file <vault>/action-items/action-items-<today>.md, even when planning tomorrow; the next briefing carries them, and their plan markers, forward.
  2. Engine. Resolve scoutctl and check that it knows planning: 
    SCOUTCTL="${SCOUT_SCOUTCTL:-}"
[ -x "$SCOUTCTL" ] || SCOUTCTL="${CLAUDE_PLUGIN_ROOT:-}/.venv/bin/scoutctl"
[ -x "$SCOUTCTL" ] || SCOUTCTL="$(command -v scoutctl)"
echo "SCOUTCTL=$SCOUTCTL"
"$SCOUTCTL" manifest show | grep -q '"planning_v1": true' && echo PLANNING_OK || echo PLANNING_UNAVAILABLE
    Every shell block starts fresh, so from here on call scoutctl by the full path this block printed. SCOUT_SCOUTCTL is for testing a plugin checkout: a claude --plugin-dir session does not reach the checkout's engine through PATH. On PLANNING_UNAVAILABLE, tell the user the engine at that path predates /scout-plan, then stop. A normal install needs /scout-update. A session testing a checkout needs Claude Code started with SCOUT_SCOUTCTL=<checkout>/.venv/bin/scoutctl.
  3. Settings and calibration. 
    SCOUT_DATA_DIR=<vault> "$SCOUTCTL" planning show --json
SCOUT_DATA_DIR=<vault> "$SCOUTCTL" planning calibration --json
"$SCOUTCTL" action-items list <today's file> --json --with-plan --include-done
    Use these values everywhere below: work_start, work_end, increment_minutes (the grid, 15 by default), capacity_pct, buffer, new_work_buffer, deep_block_minutes, batch_block_minutes, meeting_gap_minutes, event_title_prefix, event_visibility, event_availability. Never hardcode them.
  4. Calendar tools. Use the Google Calendar MCP: list_events, get_event, create_event, delete_event. If they are not loaded, find them with ToolSearch. If there is no calendar connector, say so and offer a plan without calendar blocks.

Read the full file on GitHub · 162 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. 4d ago First seen · 162 lines · 56 tokens per session scan A db72e80e3918

Subscribe to this mod's changes

scout-plan is a command published in the GitHub repository Raven-Scout/scout-plugin (17 stars, last pushed 4d ago), licensed MIT. It adds 56 tokens to every session and 3,421 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to scout-plan, differing in 0 lines, and is treated as a copy.

Autonomous AgentsPlanningProductivityagenticai-agentanthropicclaude-code-plugin
Related

Other commands, from other repositories

scout-meta-review

Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.

Raven-Scout/Scout · 61 tokens

scout-work

Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).

Raven-Scout/Scout · 47 tokens

ccc-teleport

Transfer your current Claude Code session to another device (mobile, web, desktop) using teleport.

KevinZai/commander · 19 tokens

status-updates

Configure and manage periodic status update notifications via MCP channels.

KevinZai/commander · 14 tokens

ccc-cloudcli

CloudCLI — bridge to web-based Claude Code sessions for mobile access.

KevinZai/commander · 13 tokens

ashlr-eco-mode

Toggle eco mode — aggressive token-saving behaviors that trade some response richness for lower session cost.

ashlrai/ashlr-plugin · 24 tokens