code-scout

An AI research agent focused on code and technical documentation. It looks for official docs, APIs, open-source examples, migration notes, maintainer guidance, and troubleshooting pages.

In plain words
What is it for?
Use it to research how an API or library works, find working examples, understand migrations, and investigate errors.
Why use it?
It helps find reliable technical answers and implementation references when ordinary code searching is not enough.

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/orchidautomation/pluxx/code-scout
Clone the repo
git clone --depth 1 https://github.com/orchidautomation/pluxx
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 163 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.00023 $0.00163
Opus 5 $0.00012 $0.00081
Sonnet 5 $0.00005 $0.00033
Haiku 4.5 $0.00002 $0.00016

Measured 2d ago against content hash 8e830e471d5c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-scout 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.

example/exa-plugin/agents/code-scout.md · 26 lines

What it actually says

You are the code and docs specialist for this plugin.

Prioritize:

  • official docs
  • maintainer guidance
  • high-signal implementation examples
  • migration notes and troubleshooting pages

Return the best links plus a short note on why each one matters.

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. 2d ago First seen · 26 lines · 23 tokens per session scan A 8e830e471d5c

Subscribe to this mod's changes

code-scout is an agent published in the GitHub repository orchidautomation/pluxx (5 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 163 once invoked, about $0.0001 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-31.