repo-recon

repo-recon is a skill for Claude Code from rpraharaj/forward-deployed-engineer. It costs 158 tokens per session (3,582 once invoked), scanned A, original, MIT.

A first-pass investigation of an unfamiliar codebase that maps its entry points, modules, data storage, integrations, tests, configuration, and risky areas.

In plain words
What is it for?
Use it when joining a large or inherited repository to create a durable system map and a working CLAUDE.md file.
Why use it?
It gives you a usable overview before you estimate, design, or change a system you do not yet understand.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md.

Part of the fde-core plugin — 30 skills shipped together

Good fit Use it when joining a large or inherited repository to create a durable system map and a working CLAUDE.md file.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rpraharaj/forward-deployed-engineer/repo-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.

Any agent
npx skills add rpraharaj/forward-deployed-engineer --skill repo-recon
Clone the repo
git clone --depth 1 https://github.com/rpraharaj/forward-deployed-engineer

Made for: Claude Code.

Or install fde-core, the plugin that ships this one along with the rest of its 30 skills.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/repo-recon/github.svg)](https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/repo-recon)
Your own site
<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/repo-recon"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/repo-recon/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for repo-recon

Your own site · 80×15
<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/repo-recon"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/repo-recon.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 158 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,582 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00158 $0.03582
Opus 5 $0.00079 $0.01791
Sonnet 5 $0.00032 $0.00716
Haiku 4.5 $0.00016 $0.00358

Measured 11d ago against content hash 97c0142bfbfe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

repo-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 11d 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.

fde-core/skills/repo-recon/SKILL.md · 262 lines

How it starts

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

Repo recon

The first structured pass over an unfamiliar system.

Why this exists

Dropped into a large codebase, the instinct is to start reading. After two hours you know one component and cannot answer the questions people are about to ask. This skill trades depth for coverage: where things are and what you'd be scared to touch. Depth is trace-the-flow, later, only where the work lands. A map that exists only in this session is worthless in week three.

When this applies

  • Any unfamiliar codebase you'll work in for more than a day
  • Before estimating, designing, or changing anything
  • Inheriting a system whose authors have left
  • Someone asks what a repository does and you don't know

When it doesn't

  • You already know the system — read CLAUDE.md and go
  • You need one specific fact — grep for it
  • The repository is small enough to read outright (under ~500 files)
  • You need deep behavior of a single flow — that's trace-the-flow

Prerequisites

  • Locate the workspace (../_shared/workspace-conventions.md)
  • 00-engagement.md — scopes what you're looking for
  • 00c-context.md / 01-environment.md (optional) — budget and whether it builds
  • Read ../_shared/stack-detection.md before step 2, including Searching after detection
  • On anything over ~5,000 files, apply context-strategy first and set a budget

Procedure

Ordered cheapest to most expensive. Each step should sharpen where the next one looks. Read the stopping test in step 10 before you start — it's what stops this becoming a week.

1. Shape

git ls-files | wc -l
git ls-files | sed 's/.*\.//' | tr '[:upper:]' '[:lower:]' | sort | uniq -c | sort -rn | head -20
ls -a
find . -maxdepth 2 -type d -not -path "*/.git*" -not -path "*/node_modules*" | sort
git log -1 --format="%ad %an" --date=short
git log --oneline --since="6 months ago" | wc -l

You're establishing: how big, what languages, is it alive, is it one system or several. A repository with three commits in six months and a top language you didn't expect is telling you something before you read a line.

Read the full file on GitHub · 262 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 262 lines · 158 tokens per session scan A 97c0142bfbfe

Subscribe to this mod's changes

repo-recon is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 24d ago), licensed MIT. It adds 158 tokens to every session and 3,582 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.