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/marketplace)<a href="https://agentmods.dev/plugins/raven-scout/scout/marketplace"><img src="https://agentmods.dev/badge/plugins/raven-scout/scout/marketplace/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/marketplace"><img src="https://agentmods.dev/badge/plugins/raven-scout/scout/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
scout-plugin marketplace 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 today.
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.
What it actually says
{
"name": "scout-plugin",
"owner": {
"name": "Jordan Burger"
},
"description": "Marketplace for the Scout autonomous knowledge management plugin",
"plugins": [
{
"name": "scout",
"source": {
"source": "git-subdir",
"url": "https://github.com/Raven-Scout/Scout.git",
"path": "plugin",
"ref": "stable"
},
"description": "Autonomous knowledge management and daily briefing system for Claude Code",
"version": "0.18.1",
"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"
]
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
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.
- today Changed 9c609c3b6e59
- yesterday Changed eb4fba6ae988
- 2d ago First seen · 33 lines scan A d8d7a6501173
scout-plugin marketplace is a plugin published in the GitHub repository Raven-Scout/Scout (20 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-12.
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…
hermitd-feed
Scheduled briefs for Hermit from sources you choose, with story tracking, weekly summaries, and source-quality checks.
claude-code-hermit
Your own local Claude Tag, in the Claude app, Discord, Telegram, or a custom Claude Code channel.
feed-hermit
Scheduled briefs for Hermit from sources you choose, with story tracking, weekly summaries, and source-quality checks.
brewcode
Brewcode - Claude Code authoring toolkit: skill, agent and rule creation and sync, semantic code search (semble), project conventions, E2E tests, generated review and domain-team skills, setup dashboard, post-compact plan re-anchor.
claude-mini-hud
A lightweight Claude Code status bar that shows live details such as context, token use, balance, current tasks, tools, agents, cost, Git, estimated time, and warnings. It includes 21 display themes and has no runtime dependencies.