Traces data flow from entry points to dangerous operations. Cross-file reasoning to determine which entries can reach which dangers, and what validation exists in between. MUST run on Opus for reasoning depth. Use via /sast command.
How to install sast-flow-tracer?
h-mmer/pentest-agents/sast-flow-tracer
$curl -o .claude/agents/sast-flow-tracer.md https://raw.githubusercontent.com/h-mmer/pentest-agents/HEAD/.claude/agents/sast-flow-tracer.mdInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install sast-flow-tracer by running `curl -o .claude/agents/sast-flow-tracer.md https://raw.githubusercontent.com/h-mmer/pentest-agents/HEAD/.claude/agents/sast-flow-tracer.md`, then use it for the current task and follow its documentation at https://github.com/h-mmer/pentest-agents.
Related
6 picksType
- debuggerRoot-cause analysis, regression isolation, stack trace analysis, build/compilation error resolutionJul 2026
- exploreCodebase search specialist for finding files and code patternsJul 2026
- tracerEvidence-driven causal tracing with competing hypotheses, evidence for/against, uncertainty tracking, and next-probe recommendationsJul 2026
- performance-analystThe Performance Analyst profiles game performance, identifies bottlenecks, recommends optimizations, and tracks performance metrics over time. Use this agent for performance profiling, memory…May 2026
- debuggerUse this agent when encountering errors, test failures, unexpected behavior, or any issues that require root cause analysis. The agent should be invoked proactively whenever debugging is needed.Jul 2026
- explorerRead-only code exploration sub-agent. Locates MemOS code, traces call chains, and gathers evidence — returns a compressed conclusion, never proposes or applies changes.Jul 2026
