recon

A codebase-mapping agent that identifies the main programming language, entry points, and files reachable from them. Entry points are the files or programs where execution begins.

In plain words
What is it for?
Preparing a workspace manifest before scanning, including language detection, live files, dead files, and uncertainty caused by dynamic imports or build scripts.
Why use it?
It separates code that is used from files that may be unused, so later analysis can focus on the parts of the workspace that actually matter.

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/orin-dx/agent-plugins/recon
Clone the repo
git clone --depth 1 https://github.com/orin-dx/agent-plugins
Per session 153 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 837 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.00153 $0.00837
Opus 5 $0.00077 $0.00418
Sonnet 5 $0.00031 $0.00167
Haiku 4.5 $0.00015 $0.00084

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

Security

Grade A, and why

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

plugins/ranger/agents/recon.md · 51 lines

What it actually says

Return exactly this JSON:

{
  "workspace_root": "string",
  "language": "rust|typescript|javascript",
  "live_files": ["string"],
  "dead_files": ["string"],
  "entry_points": ["string"],
  "confidence": "high|medium|low",
  "reasoning": "string"
}

WHEN dynamic imports, procedural macros, or build scripts make reachability uncertain, THE SYSTEM SHALL set confidence to medium or low and document the specific uncertainty in reasoning.

THE SYSTEM SHALL NEVER mark a file as live solely because it exists in the workspace directory. reasoning is discarded, not forwarded downstream — keep the confidence rationale to 1-2 sentences, not a narrated trace of every import followed.

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 · 51 lines · 153 tokens per session scan A e53241ebedcf

Subscribe to this mod's changes

recon is an agent published in the GitHub repository orin-dx/agent-plugins (1 stars, last pushed 5d ago), licensed MIT. It adds 153 tokens to every session and 837 once invoked, about $0.0008 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.

Related

Other agents, from other repositories

security-auditor

Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.

addyosmani/agent-skills · 35 tokens

codemap

Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…

alvinunreal/oh-my-opencode-slim · 0 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

lead

Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.

nguyenthienthanh/aura-frog · 28 tokens

replanner

Triggered by failure-classifier on F2-F4 escalations. Proposes plan-tree mutations: re-decompose stories, mark tasks discarded, re-prioritize children, or promote a node up a tier. Read-only on code; mutations applied via master-planner.

nguyenthienthanh/aura-frog · 57 tokens

geo-schema-render

Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.

greglas75/zuvo · 23 tokens