overview

A guide to using codescout with coding assistants that support MCP, a standard way for tools to connect to an agent. It compares setup and code-navigation support in Claude Code, GitHub Copilot, and Cursor.

In plain words
What is it for?
Use it to compare agent integrations, follow setup guidance, and learn how codescout supports different coding environments.
Why use it?
It helps developers understand which integrations are supported and how codescout changes the agent’s approach to finding and understanding code.

Agent

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 agents/mareurs/codescout/overview
Clone the repo
git clone --depth 1 https://github.com/mareurs/codescout
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 214 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00214
Opus 5 $0.00000 $0.00107
Sonnet 5 $0.00000 $0.00043
Haiku 4.5 $0.00000 $0.00021

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

Security

Grade A, and why

overview 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.

docs/manual/src/agents/overview.md · 24 lines

What it actually says

Agent Integrations

codescout works with any MCP-capable coding agent. Once registered as an MCP server, codescout's system prompt injects automatically into every session, giving the agent tool selection rules and iron laws for code navigation.

Feature comparison

Feature Claude Code GitHub Copilot Cursor
MCP protocol stdio stdio stdio
System prompt injection Automatic Automatic Automatic
Tool enforcement (routing plugin) Plugin with hooks Copilot Skill guidance Cursor Rules guidance
Workspace support Full Full Full
Onboarding Automatic Automatic Automatic

Guides

Agent Guide
Claude Code Claude Code — primary integration with routing plugin enforcement
GitHub Copilot GitHub Copilot — VS Code extension with Skills-based guidance
Cursor Cursor — Cursor Rules-based guidance
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 · 24 lines · 0 tokens per session scan A 877fe4980c1b

Subscribe to this mod's changes

overview is an agent published in the GitHub repository mareurs/codescout (21 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 214 tokens. 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.

Related

Other agents, from other repositories

system-architect

Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…

rtk-ai/rtk · 0 tokens

ap-preflight-probe

L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.

Spielewoy/autoprompt-skill · 39 tokens

ijfw-assumptions-analyzer

Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?

FerroxLabs/ijfw · 34 tokens

ijfw-accessibility-reviewer

Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.

FerroxLabs/ijfw · 37 tokens

ring:qa

Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.

LerianStudio/ring · 52 tokens

integration-reviewer

Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.

FlorianBruniaux/claude-code-ultimate-guide · 57 tokens