flow-trace

Trace data flow from source to sink across multiple files to map taint propagation.

1|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/MAF2414/kyco --skill flow-trace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-trace
Source: https://github.com/MAF2414/kyco/tree/main/.claude/skills/flow-trace
Command: npx skills add https://github.com/MAF2414/kyco --skill flow-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace data flow across files from source to sink to map taint propagation and support secure auditing.

Core Features & Use Cases

  • Cross-file taint tracing: map how user input propagates through the codebase to dangerous sinks.
  • Structured flow edges: generate YAML-like flow_edges for visualization and reporting.
  • Security validation and documentation: document attack paths for security reviews.

Quick Start

Run a trace across your repository to generate flow_edges for taint paths.

Frequently Asked Questions about flow-trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace data flow across multiple files to map taint propagation?

To trace data flow across multiple files, you map how user input propagates from source to dangerous sinks. This cross-file taint analysis identifies transformations and boundaries, producing structured flow edges for security auditing.

What is cross-file taint analysis and when do I need it for a security audit?

Cross-file taint analysis tracks how untrusted data flows from sources to dangerous sinks across codebase boundaries. You need this security audit technique to verify whether inputs reach vulnerable execution paths and document attack paths for review.

How do I document vulnerability paths from source to sink for code analysis?

You document vulnerability paths by mapping data flow from source to sink and generating YAML-like flow edges. These structured outputs visualize taint propagation, allowing you to verify and report on security vulnerabilities across files.

Can I verify if user input reaches dangerous sinks without manual cross-file tracing?

Yes, you can verify if user input reaches dangerous sinks by running an automated trace across your repository. The process identifies sources, follows transformations through cross-file boundaries, and confirms whether dangerous sinks are reached.

Does cross-file taint analysis work for mapping flow edges in large repositories?

Cross-file taint analysis works for large repositories by tracing data flow across file boundaries to generate structured flow edges. It maps taint propagation from source to sink, providing comprehensive security validation and documentation outputs.