version-tracker-add-target

What problem does it solve? Manually registering new bug bounty targets and their version-checking sources in a tracking database is error-prone and can create duplicate asset rows, causing redundant polling. This Skill creates target, asset, and version_source rows in one step with built-in deduplication. ## Core Features & Use Cases - One-step target registration: Creates the target row, asset rows per attack vector, target_asset junction rows, and version_source entries with the correct source_type, check_method, and config. - Structural deduplication: Reuses existing asset rows matched on (vector_type, canonical_identifier) so the same repo tracked under multiple targets is polled only once. - Custom version sources: Supports inserting custom checkers via SQL, with a template at checkers/custom/_template.py. - Use Case: After importing program scope, you discover a new GitHub org worth monitoring. Run the helper script to register the target, normalize the canonical identifier to owner/repo, and attach version sources in a single pass. ## Quick Start Ask the assistant to add a new bug bounty target to the version tracker by running the add_target.py helper script with the target's GitHub org or Play Store link.