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/plugins/raven-scout/scout/plugin)<a href="https://agentmods.dev/plugins/raven-scout/scout/plugin"><img src="https://agentmods.dev/badge/plugins/raven-scout/scout/plugin/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/plugins/raven-scout/scout/plugin"><img src="https://agentmods.dev/badge/plugins/raven-scout/scout/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
scout 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 — 94% identical, 6 lines differ
What it actually says
{
"name": "scout",
"version": "0.14.0",
"description": "Autonomous knowledge management and daily briefing system. Monitors your work tools (Slack, Calendar, Linear, GitHub, etc.), synthesizes findings into a persistent knowledge base with a formal ontology, and delivers daily action items — all running unattended via scheduled Claude Code sessions. Six session types: Morning Briefing, Consolidation, Dreaming, Research, interactive Work sessions, and Meta Review. Pre-session hooks pre-compute KB staleness, recent git activity, PR state, and Claude Code session summaries before each run, trading a few seconds of shell work for large token savings inside the session.",
"author": {
"name": "Jordan Burger"
},
"homepage": "https://github.com/Raven-Scout/Scout",
"repository": "https://github.com/Raven-Scout/Scout",
"keywords": [
"knowledge-management",
"briefing",
"automation",
"scheduling",
"obsidian"
]
}
What it installs
The manifest is a name and a version. 4 skills, 6 commands, 1 hook travel with it, and installing the plugin installs all of them — 415 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill scout-briefing A 40 tokens
- Skill scout-consolidation A 36 tokens
- Skill scout-dream A 29 tokens
- Skill scout-research A 37 tokens
- Command scout-update A 40 tokens
- Command scout-status A 28 tokens
- Command scout-plan A 56 tokens
- Command scout-meta-review A 61 tokens
- Command scout-work A 47 tokens
- Command scout-setup C 41 tokens
- Hook Stop A not measured
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 · 18 lines scan A be5e5b1e6499
scout is a plugin published in the GitHub repository Raven-Scout/Scout (19 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
scout
Autonomous knowledge management and daily briefing system. Monitors your work tools (Slack, Calendar, Linear, GitHub, etc.), synthesizes findings into a persistent knowledge base with a formal ontology, and delivers daily action items — all running unattended via scheduled Claude Code sessions. Six session types…
claude-code-hermit
Your own local Claude Tag, in the Claude app, Discord, Telegram, or a custom Claude Code channel.
pith
Token optimization for Claude Code. Automatic tool output compression (40-60% reduction), token meter in statusline, auto-compact at 70% context, structured output formats, self-building project wiki, URL ingestion, Karpathy compile pass, and semantic lint.
tools
Session lifecycle management for Claude Code — orient, checkpoint, close out, and never lose the thread between sessions.
finito
Closes a working session with a summary you can read, a handoff block for compacting now and a resume block for coming back another day.
recall
Durable, fully-local project memory for Claude Code. Logs every session to .recall/history.md and condenses it into .recall/context.md with a local Python summarizer (TF-IDF + TextRank) — no API key, no external model, nothing leaves your machine. New sessions resume from the saved context.