target-dossier

A persistent offensive security campaign directory tracks target dossiers, evidence, and request maps across multiple manual hunting sessions. It enforces impact-driven testing by attaching data to specific actors and exploit chain candidates.

The best way to track bug bounty evidence is using a persistent dossier that structures target data, request maps, and chain candidates. This prevents fragmented findings by forcing every test to attach to specific actors, objects, and states throughout the engagement.

To initialize a structured directory for pentest recon, invoke the dossier skill followed by the target domain. This automatically creates a campaign workspace with markdown files and directory hierarchies to track actors, object families, and exploit chain candidates.

No external dependencies or APIs are required. The tracker operates entirely through local file system access to manage campaign-specific markdown files and directory hierarchies, ensuring your offensive security data remains self-contained and persistent.

Yes, the dossier system is specifically designed to support manual hunting workflows for bug bounty targets. It tracks discovered vulnerabilities and maintains context on exploit chain candidates throughout the entire engagement by linking tests to actors and object families.

The primary limitation is the strict requirement for local file system access to manage campaign-specific markdown files and directory hierarchies. It does not integrate with external APIs or cloud platforms, meaning all persistent tracking relies entirely on the local environment.