skills/mental-map/SKILL.md
Use when mapping application architecture, analyzing Caido MCP proxy traffic, grouping requests into auth, cart, checkout, signup, login, forgot-password, or user-profile flows, or documenting sequence diagrams and replication notes.
npx skillsauth add ghostonbutterbread/bug-bounty-harness mental-mapInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Build mental maps of application architecture from Caido MCP proxy traffic.
Read shared state in this order before mapping flows:
notes/summary.mdnotes/observations.mdchecklist.md (auth, workflow, and business-logic items only)todo.md (workflow mapping or prerequisite items only)Use Caido MCP proxy traffic as the source of truth, set the browser or replay client proxy to KAIDO_MCP_PROXY_URL, then classify captured requests into application flows.
When the flow creates reusable routes, object references, auth boundaries, or follow-up hypotheses, also write normalized observations through /live-map so future agents can query the universal runtime application map instead of rediscovering the same area.
Prioritize end-to-end flows another agent would need to replay safely:
authsignuploginforgot-passworduser-profilecartcheckout$HARNESS_ROOT/prompts/mental-map-playbook.md$HARNESS_SHARED_BASE/{program}/agent_shared/application-structure/$HARNESS_SHARED_BASE/{program}/agent_shared/application-map/$HARNESS_ROOT/agents/live_map.py$HARNESS_ROOT/agent_shared/templates/application-structure/flow-template.mdWrite one markdown file per flow to:
$HARNESS_SHARED_BASE/{program}/agent_shared/application-structure/{flow-type}/{flow-name}.md
Each flow file must include:
prompts/mental-map-playbook.md.KAIDO_MCP_PROXY_URL and capture the real workflow.agent_shared/application-structure/{flow-type}/{flow-name}.md./live-map.notes/summary.md, notes/observations.md, and todo.md when the map exposes new testing lanes or prerequisites.documentation
Use when attacker-controlled input is saved and rendered later in a profile, comment, title, notification, admin view, export, email, feed, upload metadata, or other stored render surface.
content-media
Use when attacker-controlled input appears in the immediate HTTP response or browser-rendered page and needs reflected XSS context classification, payload selection, mutation, and browser verification.
data-ai
Use when inspecting proxy traffic from PwnFox-profiled browser sessions, filtering Caido/Burp/proxy history by X-PwnFox-Color, or interpreting user phrases like 'Red session' as a distinct browser/auth/profile lane.
tools
# LFI — Local File Inclusion Bypass ## What It Does Tests LFI bypass techniques: path traversal, null bytes, wrappers, log poisoning. Load `general-security-testing-policy`, `live-testing-policy`, and `injection-testing-policy` before live testing. For file/path sinks, absence of an immediate file read or response delta is not a stop reason by itself; use the policy to reason about path normalization, extension allowlists, wrappers, encoding, parser differences, and stack-specific proof ladder