agentmods.dev

recon CLAUDE.md

recon CLAUDE.md is an instructions file for coding agents from cappyeo/recon. It costs 486 tokens per session, scanned A, original, MIT.

Project instructions for Recon, a code-intelligence engine that builds a map of a codebase and exposes it through MCP, a standard way for AI tools to use external capabilities.

In plain words
What is it for?
Use them when working on Recon to trace execution flows, map dependencies, assess change impact, rename code safely, or query the indexed codebase.
Why use it?
They explain how to build, index, run, and maintain the project’s code-analysis system.

Instructions file

not rated 5 4mo ago A scan 486 tokens original MIT
View the source file cappyeo/recon
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/cappyeo/recon/claude-md
Clone the repo
git clone --depth 1 https://github.com/cappyeo/recon

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for recon CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/cappyeo/recon/claude-md.svg)](https://agentmods.dev/instructions/cappyeo/recon/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/cappyeo/recon/claude-md"><img src="https://agentmods.dev/badge/instructions/cappyeo/recon/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 486 This file is loaded in full into every session.
When invoked 486 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.00486 $0.00486
Opus 5 $0.00243 $0.00243
Sonnet 5 $0.00097 $0.00097
Haiku 4.5 $0.00049 $0.00049

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

Security

Grade A, and why

recon CLAUDE.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 4d 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.

CLAUDE.md · 43 lines

How it starts

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

Recon — Code Intelligence Engine

Project Overview

Recon is a lightweight code intelligence engine that builds a knowledge graph of codebases (13 languages via tree-sitter + TypeScript Compiler API) and exposes it via MCP (Model Context Protocol). It provides 14 tools, 3 prompts, and 5 resources for dependency mapping, blast radius analysis, safe rename, execution flow tracing, and graph queries.

Build & Run

npm install
npm run build          # TypeScript → dist/
npx recon index        # Index a codebase
npx recon serve        # Start MCP server on stdio

Architecture

  • src/analyzers/ — Go AST analysis, TypeScript compiler API analysis, cross-language API matching
  • src/graph/ — In-memory knowledge graph (KnowledgeGraph class with Map + adjacency index)
  • src/mcp/ — MCP server (stdio), tool definitions (RECON_TOOLS), tool handlers, next-step hints
  • src/storage/ — JSON serialization to .recon/ directory (graph.json + meta.json)
  • src/cli/ — Commander-based CLI with index, serve, status, clean commands

Key Patterns

  • Node IDs use namespaced prefixes: go:func:, ts:comp:, etc.
  • Incremental indexing via SHA-256 file hashing — unchanged files are skipped
  • Cross-language edges link TypeScript API calls to Go HTTP handlers
  • Every tool response includes a next-step hint guiding the agent to the logical next action

When Modifying

  • Tool definitions live in src/mcp/tools.ts — update both the definition and the handler in src/mcp/handlers.ts
  • The RECON_TOOLS array is the single source of truth for tool schemas
  • Graph types are in src/graph/types.ts — changing Node/Relationship interfaces affects serialization
  • Storage format is plain JSON — no migrations, just bump version in IndexMeta if schema changes

Do Not

  • Do not add dependencies without good reason — the project is intentionally lightweight
  • Do not modify the MCP protocol layer — use the @modelcontextprotocol/sdk as-is
  • Do not hardcode project-specific paths — Recon should work with any Go + TypeScript codebase

Read the full file on GitHub · 43 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. 4d ago First seen · 43 lines · 486 tokens per session scan A 6887b86734d3

Subscribe to this mod's changes

recon CLAUDE.md is an instructions file published in the GitHub repository cappyeo/recon (5 stars, last pushed 4mo ago), licensed MIT. It adds 486 tokens to every session, about $0.0024 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 instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens