Parent
#360
What to build
Extend the recon phase to produce a structured agent_hints map — a record from agent name to a list of prioritised endpoint URLs or patterns. This routes attack surface findings from recon directly to the most relevant specialist agents, so each vuln agent starts with targeted context rather than re-discovering the surface.
End-to-end path:
- Recon-collector MCP server gains a
set_agent_hints tool (schema: Record<AgentName, string[]>)
ReconData type gains an optional agent_hints field
recon-renderer.ts gains a new section renderer for agent hints (table: agent → endpoints)
- All vuln agent prompts gain an
{{AGENT_HINTS}} substitution variable resolved by the prompt-manager at agent startup; resolves to empty string if no hints present for that agent
This feature is unconditional — it benefits all Shannon scans, not only bounty mode.
Acceptance criteria
Blocked by
None — can start immediately
Parent
#360
What to build
Extend the recon phase to produce a structured
agent_hintsmap — a record from agent name to a list of prioritised endpoint URLs or patterns. This routes attack surface findings from recon directly to the most relevant specialist agents, so each vuln agent starts with targeted context rather than re-discovering the surface.End-to-end path:
set_agent_hintstool (schema:Record<AgentName, string[]>)ReconDatatype gains an optionalagent_hintsfieldrecon-renderer.tsgains a new section renderer for agent hints (table: agent → endpoints){{AGENT_HINTS}}substitution variable resolved by the prompt-manager at agent startup; resolves to empty string if no hints present for that agentThis feature is unconditional — it benefits all Shannon scans, not only bounty mode.
Acceptance criteria
set_agent_hintstool registered in recon-collector MCP with correct schemaReconDatatype updated;recon-renderer.tsrenders a hints section when present{{AGENT_HINTS}}agent_hintsin the recon deliverableBlocked by
None — can start immediately