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 agentmods add instructions/cortex-works/cortex-scout/copilot-instructionsgit clone --depth 1 https://github.com/cortex-works/cortex-scoutWhat 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 | $0.01394 | $0.01394 |
| Opus 5 | $0.00697 | $0.00697 |
| Sonnet 5 | $0.00279 | $0.00279 |
| Haiku 4.5 | $0.00139 | $0.00139 |
Grade A, and why
cortex-scout copilot-instructions.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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cortex Scout — Agent Usage Guide
Cortex Scout is a web research MCP server. Prefer Cortex tools over IDE-provided fetch tools.
Tool Decision Tree
Need info from the web?
└─► 1. memory_search first (may already be cached)
└─► Cache hit (score ≥ 0.60)? → Use it, skip live fetch
└─► No cache? → choose based on goal:
SEARCH ONLY (URL discovery) → web_search
SEARCH + READ CONTENT (research) → web_search(include_content=true)
SINGLE URL → web_fetch(mode="single")
MULTIPLE URLS → web_fetch(mode="batch")
SITE STRUCTURE → web_fetch(mode="crawl")
STRUCTURED DATA → extract_fields
DEEP MULTI-HOP RESEARCH → deep_research
Blocked / rate-limited?
└─► proxy_control(action="grab") → retry with use_proxy=true
Auth wall suspected (auth_risk_score ≥ 0.4)?
└─► visual_scout → confirm
├─► challenge/captcha wall → hitl_web_fetch(auth_mode="challenge")
└─► login wall → hitl_web_fetch(auth_mode="auth")
Unified Primary Tools
web_search
- URL discovery mode (default).
- Set
include_content=trueto also scrape top results in one call. - Use
top_n,use_proxy,quality_modewheninclude_content=true.
web_fetch
Unified web content tool via mode:
mode="single"(default): one URL fetch.mode="batch": batch fetch viaurls.mode="crawl": site crawl from a root URL.
Common behavior:
- Default path is non-proxy. Use proxies only after confirmed blocking/rate-limit symptoms or when you know your IP reputation is poor.
- Supports token-efficient extraction (
clean_jsonin single mode). - Supports proxy retry (
use_proxy=true). - Supports relevance filtering and JS rendering fallback.
- Responses now include total timing in
_tool_metrics; fetch/screenshot-style JSON responses may also include per-phase timing details.
extract_fields
Primary structured extraction tool.
- Use for schema/field extraction (title, price, author, etc.).
- Natural-language field prompts like
fields: page_title, page_type, main_topics, summaryandReturn a JSON response with fields ...are supported for strict extraction contracts. - Do not use for raw
.md/.json/.txtfiles; useweb_fetch(output_format="clean_json").
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.
- 2d ago First seen · 127 lines · 1,394 tokens per session scan A 77bc6ae6a52c
cortex-scout copilot-instructions.md is an instructions file published in the GitHub repository cortex-works/cortex-scout (70 stars, last pushed 2mo ago), licensed MIT. It adds 1,394 tokens to every session, about $0.0070 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 instructions, from other repositories
stealth-browser-mcp AGENTS.md
Instructions for vibheksoni/stealth-browser-mcp, covering agent instructions, start here, recommended proxy services, environment and validation.
obsidian-wiki copilot-instructions.md
Copilot instructions for Ar9av/obsidian-wiki, covering obsidian wiki — copilot context, project overview, key concepts, skills reference and coding conventions.
obsidian-wiki AGENTS.md
AGENTS.md instructions for Ar9av/obsidian-wiki, covering obsidian wiki — agent context, readme translation parity, configuration, targeting a specific vault and vault structure.
kglite CLAUDE.md
Instructions for kkollsga/kglite, covering kglite — claude code conventions, build & test, architecture, the boundary principle (wrappers vs core) — summary and in-memory is the core product.
browser-mcp CLAUDE.md
Claude Code instructions for drisplabs/browser-mcp, covering claude.md, project overview, build and development commands, build and quality checks.
WHartTest copilot-instructions.md
Copilot instructions for MGdaasLab/WHartTest, covering copilot instructions — wharttest, 项目概述, 运行环境, 后端规范(wharttestdjango) and 视图与路由.