Sync
Apps & AutomationsyncSync is an Agent Skill for apps & automation published in the H-mmer/pentest-agents repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Sync program scope, policy, and hacktivity from a bug bounty platform. Usage: /sync hackerone tesla or /sync bugcrowd uber
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/H-mmer/pentest-agents/blob/HEAD/providers/openclaw/.agents/skills/cmd-sync/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sync, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Sync bug bounty program data: $ARGUMENTS
Parse the arguments as: <program_handle>
- Use the
bounty-platformsMCP server toolsync_programwith the platform and program handle. This fetches scope, policy, and hacktivity and writes them to the current directory. - After sync completes, run
uv run python3 ../../tools/brain.py initif brain isn't initialized yet. - Read the generated
scope.yamlandhacktivity.mdfiles. - Update the brain with key intelligence from hacktivity:
- Run
uv run python3 ../../tools/brain.py log "Synced program data from <platform>/<program>" - If hacktivity shows common vulnerability types, note them as priority areas
- If hacktivity shows many duplicates of a type, note them as areas to avoid
- Run
- Summarize: scope overview, policy highlights (restrictions, safe harbor), and hacktivity patterns (most common vuln types, average bounties).
Top-Tier Sync Standard
Policy is hunting input, not paperwork.
Extract and persist:
- exact in-scope assets, wildcard rules, mobile/API/cloud qualifiers, and third-party exclusions
- required headers, user-agent, testing accounts, sandbox rules, rate limits, and forbidden actions
- severity exclusions and never-pay classes
- payout hints from hacktivity: accepted classes, duplicate-heavy classes, bounty tiers, triage language
- newly added or removed assets since last sync
End with a hunt bias: where the program appears to pay, where it appears saturated, and what proof standard the policy implies.