scout AGENTS.md

Repository instructions for Scout, an enterprise context agent that gathers information from sources such as local files, a CRM, wikis, Slack, Google Drive, and MCP servers. MCP is a standard way to connect an agent to external tools and data.

In plain words
What is it for?
Use them when working on Scout's source connectors, database reads and writes, wiki access, Slack or Drive access, MCP tools, or the single-agent request flow.
Why use it?
They describe how Scout is structured and which sources can be read or updated, helping developers change the correct context provider without breaking the agent's data flow.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/agno-agi/scout/agents-md
Clone the repo
git clone --depth 1 https://github.com/agno-agi/scout

Made for: Codex, OpenCode.

Per session 3,932 This file is loaded in full into every session.
When invoked 3,932 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.03932 $0.03932
Opus 5 $0.01966 $0.01966
Sonnet 5 $0.00786 $0.00786
Haiku 4.5 $0.00393 $0.00393

Measured yesterday against content hash be13eb8b51bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

scout AGENTS.md 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 yesterday.

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.

AGENTS.md · 249 lines

How it starts

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

AGENTS.md

Project Overview

Scout is an enterprise context agent — a single agno.Agent with N ContextProviders. Ships with WebContextProvider, WorkspaceContextProvider (local files via agno.tools.Workspace), DatabaseContextProvider (the CRM — user's contacts/projects/notes/follow-ups), two WikiContextProviders (a writable knowledge wiki and a read-only voice wiki), SlackContextProvider, GDriveContextProvider, and MCPContextProvider (any MCP server → one query_mcp_<slug> tool on Scout). GitHub, Gmail, and Calendar land in the next release (were built and verified on the feat/slack-interface branch; dropped from the ship slice until we can test end-to-end with real tokens).

Architecture

Scout (single Agent — one LLM hop per turn)
  tools = <query_|update_ tools from every registered ContextProvider> + list_contexts

Every source is a ContextProvider. The database is a provider too: DatabaseContextProvider exposes query_crm (reads) + update_crm (writes), each backed by a dedicated sub-agent so the read path never sees the write engine.

ContextProvider

agno.context.provider defines the base. Every external source subclasses ContextProvider and implements:

  • query(question) -> Answer / aquery(question) -> Answer — natural-language read
  • status() -> Status / astatus() -> Status — is the source reachable?

Providers that support writes override aupdate(instruction) -> Answer (and optionally update). The base raises NotImplementedError; _update_tool() translates that into a readable " is read-only" error so calling agents see a clean failure. Today only DatabaseContextProvider overrides it.

mode controls how the provider surfaces itself to the calling agent:

Mode Exposure
default The provider's recommended exposure. Each subclass decides.
agent One query_<id> tool wrapping a sub-agent.
tools The underlying tools directly.

model swaps the model used by the internal sub-agent (when one is built). instructions() returns mode-aware usage guidance for the calling agent.

Read the full file on GitHub · 249 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. yesterday First seen · 249 lines · 3,932 tokens per session scan A be13eb8b51bc

Subscribe to this mod's changes

scout AGENTS.md is an instructions file published in the GitHub repository agno-agi/scout (719 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 3,932 tokens to every session, about $0.0197 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.