zz-code-recon

Builds layered architectural context of codebases for security audits and vulnerability analysis.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Kaleb-Rupe/aurora --skill zz-code-recon-kaleb-rupe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zz-code-recon
Source: https://github.com/Kaleb-Rupe/aurora/tree/main/system/aurora-bridge/.claude/skills/code-recon
Command: npx skills add https://github.com/Kaleb-Rupe/aurora --skill zz-code-recon-kaleb-rupe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security auditors and code reviewers waste hours orienting themselves in unfamiliar codebases before they can find vulnerabilities. This Skill provides a structured, phased reconnaissance methodology that builds understanding from high-level architecture down to individual security-critical functions. ## Core Features & Use Cases - Phased Recon Methodology: Five phases covering overview, architecture mapping, module deep dives, function-level analysis, and detail reconnaissance, each with concrete shell commands and templates. - Trust Boundary & Entry Point Mapping: Systematically identifies where trust levels change, enumerates HTTP/WebSocket/CLI/queue entry points, and traces data flows through the system. - Ready-Made Audit Artifacts: Includes a recon checklist, a security question bank organized by domain, a context document template, and a complete FastAPI walkthrough example. - Use Case: Before auditing a new web application, run the recon phases to produce a Security Context Document listing the tech stack, entry points, critical functions, and high-risk areas, then focus deep testing on the identified priorities. ## Quick Start Ask the AI to perform a code recon on this repository and produce a security context document covering the architecture, trust boundaries, entry points, and highest-risk areas.

Frequently Asked Questions about zz-code-recon

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

FAQPage Schema
How do I build architectural context before a security audit?

Follow a top-down phased approach: identify the tech stack and dependencies, map the architecture and trust boundaries, enumerate all entry points, then analyze security-critical functions. Document findings in a structured context document as you go.

How to map entry points and trust boundaries in a codebase?

Grep for route decorators, CLI commands, and event handlers to enumerate entry points, then diagram where trust levels change such as internet to gateway, gateway to services, and services to database. Record the controls and risks at each boundary.

What should a security context document include?

Include the technology stack, architecture diagram, trust boundaries, entry point inventory, authentication and authorization mechanisms, critical functions, data flows, security controls summary, high-risk areas, and open questions requiring investigation.

Does this recon methodology work for smart contracts?

Yes, the question bank and advanced techniques cover smart contract specifics including access control, storage layout analysis, bytecode verification, event log analysis, reentrancy risks, and economic attack surfaces like flash loans and oracle manipulation.

When is static code recon not enough for security analysis?

When behavior depends on runtime state, use dynamic techniques like traffic capture with mitmproxy, debug-mode logging, database schema extraction, and API schema introspection. The advanced techniques document covers these dynamic analysis integrations.