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 --skill scout-askgit 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/skills/raven-scout/scout/scout-ask)<a href="https://agentmods.dev/skills/raven-scout/scout/scout-ask"><img src="https://agentmods.dev/badge/skills/raven-scout/scout/scout-ask/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/scout-ask"><img src="https://agentmods.dev/badge/skills/raven-scout/scout/scout-ask.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.00131 | $0.01404 |
| Opus 5.5 | $0.00052 | $0.00562 |
| Sonnet 5.5 | $0.00026 | $0.00281 |
| Haiku 4.5 | $0.00013 | $0.00140 |
Grade A, and why
scout-ask 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Asking Scout
Scout has already done the investigation. Every KB file is a synthesis that a prior session built from live connectors and stamped with the date it was verified. Answering is retrieval against a canonical file, not a fresh investigation, and the vault is laid out so one file holds the answer.
Work the three steps in order. Most questions are done after step 2. Every path below is relative to the vault root.
1. Resolve the entity to its canonical file
One cheap listing beats a vault-wide search. For a project or initiative:
ls knowledge-base/projects/ # match the user's words to a slug
The listing also shows projects.md (the registry) and archived/. Neither is a project; look inside archived/ only when the user asks about a finished or shelved project.
Then read knowledge-base/projects/<slug>/<slug>.md. That single file is the canonical record: it carries the header status and every dated update in reverse-chronological order.
Use the map below for other entity types. When the entity resolves to a file, you are done searching: read it and go to step 2.
When nothing matches, search the entity files rather than the vault:
rg -l -i "<entity>" knowledge-base/projects knowledge-base/topics knowledge-base/sources knowledge-base/people knowledge-base/ontology/entities
Never read knowledge-base/knowledge-base.md whole: on older vaults it runs to hundreds of thousands of tokens. Reach it only through a scoped rg with line numbers, after the entity files come up empty.
2. Read the freshness gate, then answer
Two timestamps sit at the top of the file. The frontmatter's last_updated: is the last substantive change. The **Last verified:** <timestamp> (<session type>) line under the title, where present, is the last time a session checked the file against its sources even if nothing changed. Gate on the newer of the two:
- Recently verified: answer from the file and cite the timestamp. The recorded state is the current state; a live re-query returns the same facts and costs several turns.
- Old enough that the answer could mislead, or neither timestamp present: answer from the file, say how old it is, and offer to drill.
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 First seen · 75 lines · 131 tokens per session scan A 8ec516ed1c9c
scout-ask is a skill published in the GitHub repository Raven-Scout/Scout (20 stars, last pushed today), licensed MIT. It adds 131 tokens to every session and 1,404 once invoked, about $0.0005 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-27.
Other skills, from other repositories
scout-consolidation
Launch a Scout consolidation session as a background process. Runs a lighter delta scan — captures what changed since the last run and updates action items and KB.
scout-dream
Launch a Scout dreaming session as a background process. Processes feedback, does KB deep work, and works on wishlist items.
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.
answer-open-question-with-alternative
Record a chosen alternative from an open question's embedded analysis as that question's answer in the current milestone's requirements.md.
discuss-new-task
Clarify a rough or ambiguous issue into one or more well-defined, task-sized pieces ready to add to the current milestone's task list.