opengrep-code-recon

Scans project source code to map tech stack, data flows, and security sinks into a CODE_RECON.md report.

9|2|Updated Jul 15, 2026
One-click install
npx skills add https://github.com/IgorSasovets/devsecops-with-claude --skill opengrep-code-recon-igorsasovets
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opengrep-code-recon
Source: https://github.com/IgorSasovets/devsecops-with-claude/tree/main/opengrep-rules-creator/.claude/skills/OPENGREP_CODE_RECON
Command: npx skills add https://github.com/IgorSasovets/devsecops-with-claude --skill opengrep-code-recon-igorsasovets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing precise, low-false-positive Opengrep rules requires deep knowledge of a codebase's entry points, taint sources, sinks, and sanitizers, which is slow to gather manually. This Skill automates that reconnaissance, producing a structured CODE_RECON.md that feeds directly into the rule-creation stage. ## Core Features & Use Cases - Multi-language codebase mapping: Detects languages, frameworks, and locales across JS/TS, Python, Java/Kotlin, Go, PHP, Swift, and Dart projects using Grep/Glob-first scanning. - Security-focused inventory: Maps HTTP entry points, taint sources, dangerous sinks (SQL, command, template, deserialization, XSS), validators, auth boundaries, crypto usage, hardcoded secrets, and DB schemas. - Auto-scaling depth: Adjusts scan depth (fast/balanced/deep) based on file count, with sampling for very large repositories, and redacts credential values in output. - Use Case: Point it at a large Express.js monorepo to enumerate all routes, raw SQL queries, and missing input validation, then hand the generated CODE_RECON.md to /opengrep-rule-creator to write targeted rules. ## Quick Start Ask the AI to recon the codebase at ./my-project with balanced depth and produce the CODE_RECON.md report for Opengrep rule creation.

Frequently Asked Questions about opengrep-code-recon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan a codebase before writing Opengrep rules?▼

Run the recon stage against your project root to generate CODE_RECON.md, which inventories languages, frameworks, entry points, taint sources, sinks, and sanitizers. This report is then consumed by the rule-creator stage to write precise, low-false-positive rules.

What languages does codebase recon for static analysis support?▼

It supports JavaScript, TypeScript, Python, Java, Kotlin, Go, PHP, Swift, and Dart. Languages are auto-detected via file markers like package.json, go.mod, or pubspec.yaml, or restricted with the --lang flag.

Does the recon scan modify or execute my source code?▼

No, the scan is strictly read-only. It uses Glob and Grep for discovery plus targeted head or grep reads for extraction, never executes target code, and stays within the specified target directory.

How does scanning scale for very large repositories?▼

Depth auto-scales by file count: deep under 200 files, balanced up to 2000, and fast beyond that. At fast depth with over 5000 files, it samples recently modified and random files per language and notes the sampling in the report.

Are hardcoded secrets exposed in the recon report?▼

No, credential values are redacted. The report records only file and line references for potential hardcoded secrets, never the actual secret values.