version-tracker-discover

Re-discover relocated version sources after structural failures in version checkers.

1|Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework --skill version-tracker-discover-maybe4a6f7365
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-tracker-discover
Source: https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework/tree/main/version-tracker/skills/version-tracker-discover
Command: npx skills add https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework --skill version-tracker-discover-maybe4a6f7365

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Version checkers break silently when a vendor moves their changelog, restructures a page, or removes an RSS feed. This Skill probes known patterns to find where version information now lives and updates the version_source configuration so monitoring resumes. ## Core Features & Use Cases - Pattern-based probing: Runs ordered discovery patterns per vector type (github_repository, website, api, android_app, ios_app, rss), checking releases, tags, common changelog paths, feeds, and version endpoints. - Database re-integration: Writes research notes, updates version_source rows with new source_url and config, and re-enables sources with consecutive_failures reset. - Safe defaults: Marks discovered sources as verification_status='unverified' with a discovery_confidence note, and supports a --dry-run mode that probes without touching the database. - Use Case: A daily check reports STORAGE_MOVED for a GitHub repository. Invoke the discovery script for that asset to probe /releases, /tags, and GitHub search, then automatically re-point the version source to the new location. ## Quick Start Run the discovery script for the broken asset to probe known patterns and update its version source, for example by asking the agent to re-discover where the asset publishes versions now.

Frequently Asked Questions about version-tracker-discover

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

FAQPage Schema
How do I re-discover a version source after a checker breaks?

Run the discover script with the asset ID, for example python3 discover.py <asset_id>. It probes known patterns for the source's vector type, writes a research note, and updates the version_source row with the new URL and config.

What triggers automatic version source discovery?

Discovery triggers when the daily check runner reports should_rediscover=True, or when error_classification.auto_action is 'trigger_discovery' and consecutive_failures reaches max_retries. It can also be invoked manually per asset or with --all-triggered.

Can I test version discovery without changing the database?

Yes, use the --dry-run flag with the asset ID. The script probes candidate sources and reports findings but does not write research notes or update version_source rows.

Does the discovery script trust newly found sources automatically?

No. Discovered sources are written with verification_status='unverified' and a discovery_confidence value in the research note. A human or follow-up process should confirm the source before relying on it.

Why does GitHub discovery hit rate limits?

The GitHub search API allows 10 requests per minute unauthenticated and 30 per minute authenticated. Set a GITHUB_TOKEN environment variable to raise the limit and avoid throttling during discovery runs.