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.
npx skills add Raven-Scout/scout-plugin --skill scout-researchgit clone --depth 1 https://github.com/Raven-Scout/scout-pluginWrote 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/skills/raven-scout/scout-plugin/scout-research)<a href="https://agentmods.dev/skills/raven-scout/scout-plugin/scout-research"><img src="https://agentmods.dev/badge/skills/raven-scout/scout-plugin/scout-research/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/skills/raven-scout/scout-plugin/scout-research"><img src="https://agentmods.dev/badge/skills/raven-scout/scout-plugin/scout-research.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.00037 | $0.00217 |
| Opus 5 | $0.00018 | $0.00109 |
| Sonnet 5 | $0.00007 | $0.00043 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
scout-research 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 10d 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.
What it actually says
Launch a SCOUT research session as a background process on this machine.
Do the following steps:
-
Run
nohup bash ~/Scout/run-research.sh > /dev/null 2>&1 &to launch the research session in the background. Capture the PID. -
Find the most recent log file:
ls -t ~/Scout/.scout-logs/research-*.log | head -1 -
Report to the user:
- Confirm the research session is running and show the PID
- Show the log file path so they can tail it if they want:
tail -f <log_file> - Remind them that research sessions typically take 10-15 minutes and cover: selecting research targets from the queue and KB entities, deep web research, knowledge integration into entity files, and a Slack summary DM when done.
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.
- 10d ago First seen · 18 lines · 37 tokens per session scan A 53c89bcf636a
scout-research is a skill published in the GitHub repository Raven-Scout/scout-plugin (16 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 217 once invoked, about $0.0002 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.
Other skills, from other repositories
returns-policy
Answer return, refund, and warranty questions for electronics. Use when the user mentions returns, refunds, RMAs, warranty coverage, damaged items, or opened packaging.
technical-troubleshooting
Provide setup, troubleshooting, and maintenance guidance. Use when the user reports a device that won't power on, connectivity issues, setup questions, overheating, or maintenance concerns.
debt-ops-init
Write or refresh a "Tech debt operations" section in the project's AGENTS.md so the team shares one source of truth for debt-ops disciplines. Run ONLY when the user explicitly asks to set up, install, or initialize debt-ops disciplines — never auto-invoke. Idempotent; only the managed section changes, other sections…
debt-ops-metrics
Print a debt-ops health summary from the metrics log, covering registration rate, feedback action rate, ADR creation, and AI-authored share. Use when the user asks for "debt-ops metrics", "debt health", "registry stats", or a tech-debt health summary. Read-only, never writes the log.
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…
capture-milestone-principle-updates
Distill reusable answering principles from a named milestone's recorded decisions into the project-wide principle store.