recon-tool-integration

When to Use

• Adding a brand-new scanning/enrichment tool to the scan pipeline.

For adding AI decision-making to an existing tool, use recon-ai-enrichment. For the graph write, use graph-db-writes. For the settings, use project-settings-cascade. This skill is the module + pipeline wiring.

Critical Rules

• NEVER ship the enrichment module without its _isolated wrapper. run_<tool>_enrichment_isolated() is the actual call path for the GROUP 3b parallel fan-out AND for every unit test; the plain run_<tool>_enrichment() alone is never fan-out-safe. Reference: recon/main_recon_modules/censys_enrich.py:369.
• NEVER vary the top-level result key. The module writes combined_result["<tool>"] and the wrapper returns snapshot.get("<tool>", {}) with the same identifier used everywhere else in the pipeline (censys_enrich.py:365).
• NEVER collect a field and not write it to the graph. Every field in the output dict must land on a node/relationship or it is silent data loss - see graph-db-writes.
• NEVER add a tool setting without updating BOTH preset layers. Add it to the Zod recon-preset-schema.ts and to RECON_PARAMETER_CATALOG in webapp/src/app/api/presets/generate/route.ts. Miss the Zod schema and AI-generated presets silently strip the setting; miss the catalog and the preset LLM never knows the tool exists.
• ALWAYS prefix every print() log [symbol][ToolName] ([*] progress, [+] success, [-] skipped, [!] error). Recon stdout is tailed into the SSE recon drawer; a bare print() is invisibly formatted.
• ALWAYS place a fan-out tool behind the deep-copy _isolated wrapper and in the correct execution group in recon/main.py; never parallelize across a dependency boundary (a tool needing live URLs cannot run before GROUP 4).