scout-meta-review

scout-meta-review is a command for Claude Code from Raven-Scout/scout-plugin. It costs 61 tokens per session (2,330 once invoked), scanned A, original, MIT.

An interactive audit of the Scout system, which runs different sessions for tasks such as briefings, research, and knowledge-base maintenance. It checks the system as a whole rather than reviewing one session.

In plain words
What is it for?
It checks recent session activity, mistake-audit trends, improvement proposals, knowledge-base health, and data-source coverage. It is intended for weekly checks or troubleshooting.
Why use it?
It helps find sessions that are not running, stalled improvements, unhealthy knowledge-base files, or uneven data coverage before those problems accumulate.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions Claude Code.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is cd <SCOUT_DIR> && python knowledge-base/ontology/parser.py stats.

Part of the scout plugin — 4 skills, 5 commands, 1 hook shipped together

Good fit It checks recent session activity, mistake-audit trends, improvement proposals, knowledge-base health, and data-source coverage. It is intended for weekly checks or troubleshooting.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Raven-Scout/scout-plugin
agentmods
npx agentmods add commands/raven-scout/scout-plugin/scout-meta-review

Made for: Claude Code.

Or install scout, the plugin that ships this one along with the rest of its 4 skills, 5 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-meta-review

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/raven-scout/scout-plugin/scout-meta-review"><img src="https://agentmods.dev/badge/commands/raven-scout/scout-plugin/scout-meta-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 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,330 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 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.00061 $0.02330
Opus 5 $0.00030 $0.01165
Sonnet 5 $0.00012 $0.00466
Haiku 4.5 $0.00006 $0.00233

Measured 12d ago against content hash b3e15581fe8b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

scout-meta-review 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 12d 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.

commands/scout-meta-review.md · 252 lines

How it starts

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

Scout Meta Review

Run an interactive Scout Meta Review — a system-level audit that sits ABOVE the individual session types (briefing, consolidation, dreaming, research, work).

This is NOT a Scout session. It does not read SKILL.md or DREAMING.md. It reviews the Scout system itself: are all the parts working together? Are improvements actually improving things? Is anything rotting, stalling, or drifting?

Run this in the current conversation so the user has full visibility. Run it weekly, or whenever something feels off.


Phase 1: System Health Check

Read scout-config.yaml first to locate the Scout directory (scout_dir) and the user's Slack ID (if Slack is enabled).

1a: Session Execution Audit

Check whether Scout sessions are actually running and completing:

# Count sessions by type in the last 7 days
for type in scout dreaming research; do
  echo "=== $type ==="
  ls -1 <SCOUT_DIR>/.scout-logs/${type}-*.log 2>/dev/null | while read f; do
    mod=$(stat -f '%Sm' -t '%Y-%m-%d' "$f" 2>/dev/null || stat -c '%y' "$f" 2>/dev/null | cut -d' ' -f1)
    echo "$mod $(basename "$f")"
  done | sort -r | head -20
done
# Check for failures
cat <SCOUT_DIR>/.scout-logs/failures.log 2>/dev/null | tail -20
# macOS: check launchd. Linux: check cron.
launchctl list | grep -i scout 2>/dev/null || crontab -l 2>/dev/null | grep -i scout || echo "No scheduled jobs found"

Report:

  • Sessions per day by type (last 7 days)
  • Failure rate (failures / total runs)
  • Any session types not running at all
  • Gaps in schedule (e.g., no afternoon consolidation for 3 days)

1b: Git Health

cd <SCOUT_DIR> && git log --oneline --since="7 days ago" | head -30
cd <SCOUT_DIR> && git status
  • Are sessions committing? Average commits per day?
  • Any uncommitted changes lingering?
  • Commit message patterns — are they following conventions (briefing [HH:MM]:, dreaming [HH:MM]:, work [HH:MM]:)?

1c: Budget & Cost

Read the full file on GitHub · 252 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. 12d ago First seen · 252 lines · 61 tokens per session scan A b3e15581fe8b

Subscribe to this mod's changes

scout-meta-review is a command published in the GitHub repository Raven-Scout/scout-plugin (16 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 2,330 once invoked, about $0.0003 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.