ptb-composability

Assess PTB composability risks in Sui smart contracts.

276|56|Updated Mar 16, 2026

Search Tags:#composability #security-audit #smart-contract #multistep #sui #ptb

Ready to run

npx skills add https://github.com/PlamenTSV/plamen --skill ptb-composability

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ptb-composability
Source: https://github.com/PlamenTSV/plamen/tree/main/agents/skills/sui/ptb-composability
Command: npx skills add https://github.com/PlamenTSV/plamen --skill ptb-composability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PTB composability in Sui enables atomic multi-command sequences but can introduce security risks if public functions are too broadly exposed or misused across commands, potentially enabling attackers to manipulate state or route assets within a single transaction.

Core Features & Use Cases

Identify which protocol functions are public and usable within PTB workflows to surface exposure points.
Model single-call assumptions, value routing, and multi-step sequencing to reveal ordering and routing vulnerabilities.
Provide mitigations and best practices for safe PTB design in Sui modules, including access control and explicit transfer guarantees.

Quick Start

Run a PTB composability audit on your Sui module to identify public functions, potential single-call and value-routing vulnerabilities, and suggested mitigations.

Frequently Asked Questions about ptb-composability

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

FAQPage Schema

What is PTB composability in Sui smart contracts and why is it a security risk?▼

Sui PTB composability allows atomic multi-command sequences but introduces security risks if public functions are broadly exposed, enabling attackers to manipulate state or route assets within a single transaction.

How do I audit Sui PTB composability for safe transactions?▼

Audit Sui PTB composability by inventorying public and entry functions, analyzing single-call assumptions, return-value routing, and multi-step sequencing to reveal attack surfaces and provide actionable mitigations.

What vulnerabilities are caused by single-call assumptions and return-value routing in Sui PTBs?▼

Single-call assumptions and return-value routing in Sui PTBs create ordering and routing vulnerabilities, allowing attackers to manipulate state by routing assets through exposed public functions across multiple commands.

What are the best practices for secure PTB design in Sui modules?▼

Best practices for secure Sui PTB design include implementing strict access control, explicit transfer guarantees, and sequencing checks to prevent unauthorized state manipulation and asset routing across transaction blocks.

How do I identify which protocol functions are exposed to PTB workflows in Sui?▼

Identify exposed protocol functions by inventorying all public and entry functions in your Sui smart contracts, then modeling their multi-step sequencing to determine which functions can be manipulated within PTB workflows.