exploration-crew

Automate Rust crate path exploration with fuzzing and symbolic/concolic execution.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sahajamoth/apex --skill exploration-crew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exploration-crew
Source: https://github.com/sahajamoth/apex/tree/main/.agents/skills/exploration-crew
Command: npx skills add https://github.com/sahajamoth/apex --skill exploration-crew

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates robust exploration of program paths to uncover edge cases and potential vulnerabilities using fuzzing and symbolic/concolic execution.

Core Features & Use Cases

  • Coordinates fuzzing, symbolic, and concolic tooling across crates/apex-fuzz, apex-symbolic, and apex-concolic.
  • Enforces ownership constraints: cannot edit files outside owned paths; prioritizes performance with optional heavy dependencies behind feature flags.
  • Supports robust testing workflows using standard Rust test patterns and integration tests for dynamic path exploration scenarios.

Quick Start

Run the exploration crew to fuzz and symbolically analyze the codebase paths within crates/apex-fuzz, crates/apex-symbolic, and crates/apex-concolic.

Frequently Asked Questions about exploration-crew

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

FAQPage Schema
How do I automate fuzzing and symbolic execution to explore program paths in Rust?

Automate dynamic path exploration by coordinating fuzzing and symbolic or concolic execution across Rust crates to uncover edge cases, performance issues, and security gaps. Use standard Rust testing patterns like #[cfg(test)] modules for integration.

What is concolic execution used for in software testing?

Concolic execution combines concrete and symbolic execution to drive deep program path exploration. It automates uncovering hidden edge cases and potential vulnerabilities in software testing workflows.

How do I set up dynamic path exploration workflows in Rust?

Set up dynamic path exploration workflows using standard Rust testing patterns within owned paths. Run coordinated fuzzing and symbolic analysis across designated crates like apex-fuzz, apex-symbolic, and apex-concolic.

Can I use fuzzing and symbolic execution without adding heavy dependencies to my Rust project?

Yes, you can keep heavy dependencies optional by placing them behind feature flags. The dynamic path exploration workflow enforces ownership constraints and prioritizes performance by editing only within owned paths.

What is the best way to find security gaps and edge cases across multiple Rust crates?

The best way to find security gaps is applying fuzzing-driven dynamic path exploration. Coordinating fuzzing, symbolic, and concolic tooling across crates uncovers edge cases and vulnerabilities effectively.

What are the limitations of using dynamic path exploration for software testing?

Dynamic path exploration is constrained by ownership boundaries, meaning it cannot edit files outside owned paths. Additionally, integrating heavy tooling dependencies requires careful management using optional feature flags.