# sast-flow-tracer

sast-flow-tracer traces data propagation from attack entry points to dangerous operations and maps every validation step in between.

- subagent · `type=agent` · Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop) · ★ 1298 repo stars
- Author: H-mmer
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/H-mmer/pentest-agents/tree/HEAD/.claude/agents/sast-flow-tracer.md
- Updated: 2026-06-12
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/sast-flow-tracer

## What it does

The subagent serves as a connector between discovered input sources and risky code sinks. It follows call paths across separate files, observing variable renames, type conversions, pointer dereferences, and macro expansions.

While following data paths, it grades each chain as Hot, Warm, or Cold depending on whether the intermediate sanitization is missing, fragile, or complete. Output reports are stored inside the `sast-work/` folder as structured JSON files.

The subagent relies on `entries.json` and `dangers.json` being present before execution. Because deep contextual reasoning is required for tracing complex call graphs, the agent specification explicitly assigns Claude Opus.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/sast-flow-tracer.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/sast-flow-tracer.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/sast-flow-tracer.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/H-mmer/pentest-agents/tree/HEAD/.claude/agents/sast-flow-tracer.md

## When to use it
- trace untrusted inputs through complex call graphs to dangerous sinks
- catalog sanitization checks and type cast truncations across files
- identify tainted variables in PHP superglobals and session scopes
- evaluate whether boundary validations prevent exploits

## Example prompts
- Run /sast to trace data flows from entries.json to critical operations
- Map the validation chain from packet parsing down to memory copy
- Track tainted $_GET parameters across included files to database queries

## Similar
- [sast-scanning](https://affpapa.org/en/nevibecode/skills/sast-scanning.md) — skill · 415 installs
- [cpg-analysis](https://affpapa.org/en/nevibecode/skills/cpg-analysis.md) — skill · 175 installs
- [security-scanning-security-sast](https://affpapa.org/en/nevibecode/skills/security-scanning-security-sast.md) — skill · ★ 50109 repo stars
- [security-sast](https://affpapa.org/en/nevibecode/commands/security-sast.md) — command · ★ 42780 repo stars
- [sast-configuration](https://affpapa.org/en/nevibecode/skills/sast-configuration.md) — skill · 10800 installs
- [triage](https://affpapa.org/en/nevibecode/skills/anthropics-triage.md) — skill · 1200 installs

From the same set: [h-mmer/pentest-agents](https://affpapa.org/en/nevibecode/by/h-mmer/pentest-agents.md) — 43 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
