Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Raven-Scout/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/scout-work)<a href="https://agentmods.dev/commands/raven-scout/scout/scout-work"><img src="https://agentmods.dev/badge/commands/raven-scout/scout/scout-work/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.
<a href="https://agentmods.dev/commands/raven-scout/scout/scout-work"><img src="https://agentmods.dev/badge/commands/raven-scout/scout/scout-work.svg" alt="Reviewed on agentmods" width="80" 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.00047 | $0.01735 |
| Opus 5.5 | $0.00019 | $0.00694 |
| Sonnet 5.5 | $0.00009 | $0.00347 |
| Haiku 4.5 | $0.00005 | $0.00173 |
Grade A, and why
scout-work 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 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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- scout-work — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scout Work Session
Run an interactive Scout work session to knock items off today's action items list.
Unlike /scout-briefing, /scout-consolidation, /scout-dream, and /scout-research (which run as background processes), this runs in the current conversation. You present actionable items one at a time with a recommended action ready to go, and wait for approval before executing.
The goal: the user decides, Scout drafts and executes. Never send a message, merge a PR, create a meeting, or take any externally-visible action without explicit approval.
Phase 1: Load & Filter
-
Get today's date in the user's timezone. Read
scout-config.yamlfor thetimezonefield (defaultAmerica/New_Yorkif missing):TZ=<timezone> date '+%Y-%m-%d' -
Read today's action items file:
<SCOUT_DIR>/action-items/action-items-YYYY-MM-DD.md- If it doesn't exist, tell the user: "No action items file for today. Run
/scout-briefingor/scout-consolidationfirst to generate one." - Stop here if no file.
- If it doesn't exist, tell the user: "No action items file for today. Run
-
Parse the file and collect all unchecked items (
- [ ]) from these sections:- 🔴 Urgent / Time-Sensitive
- 🟡 To Do
- Personal
-
Skip items from the 🟢 Watching section — those are monitoring, not actionable.
-
Skip items explicitly described as blocked by another item (e.g., "Blocked by PROJ-2630", "Waiting on Legal review").
-
Present a numbered summary:
Found N actionable items: - X urgent - Y to do - Z personal Ready to start?
Wait for the user to confirm before proceeding.
Phase 2: Work Loop
Process items in priority order: Urgent first, then To Do, then Personal.
For each item, do the following:
Step 1: Triage — classify the action type
Use the user's connected tools to determine what kind of action this is. The matrix below is a starting point — use judgment when an item spans multiple categories.
| Type | Tools to use | Signals in the item |
|---|---|---|
| GitHub | gh CLI (pr view, pr merge, pr review) |
PR #, merge, reviewer, CI, GitHub URL |
| Slack | Slack MCP (slack_send_message, slack_read_channel, etc.) | Slack DM, reply, post, thread, channel name |
| Calendar | Google Calendar MCP (create_event, list_events) | Schedule, meeting, invite, calendar |
| Linear | Linear MCP (save_issue, get_issue) | Linear issue ID, status update, create issue |
| Gmail MCP (create_draft, send_message) | Email, reply, draft, follow-up with an email address | |
| Research | WebSearch, WebFetch | Research, look up, find out, investigate, compare |
| Compound | Multiple of the above | Item needs several steps in sequence |
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.
- 3d ago First seen · 158 lines · 47 tokens per session scan A f2383057785d
scout-work is a command published in the GitHub repository Raven-Scout/Scout (19 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 1,735 once invoked, about $0.0002 per session on Opus 5.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-10-06.
Other commands, from other repositories
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).
pm-learn
Auto-extract repeatable patterns, decisions, and cost outliers from the current session and append to .great-pm/lessons.md. Promotes ≥3-occurrence patterns to /.great-pm/decisions.md. Runs continuous-learner.
pm-save
Extract lessons from this session and save them to .great-pm/lessons.md. Optional cross-project promotion to /.great-pm/decisions.md for patterns seen 3+ times (proposed, never auto-promoted).
pm-resume
Pick up where you left off. Reads .great-pm/HANDOFF.md (auto-saved by the PreCompact hook) and orients you with the next concrete step.
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.
triage
Process the user-feedback queue — triage new reports, keep the status mirror honest, and (at release time only) send the shipped emails.