delqhi/sin-bugbounty
0
SIN-BugBounty
SIN-BugBounty is a SIN A2A agent package for the Silicon Workforce.
Identity
- Slug:
sin-bugbounty - Team:
Team - Coding - Team Manager:
SIN-Coding-CEO - Purpose: Elite bug bounty hunter agent that scans OpenAI, Google, and major security portals for highest-paying vulnerabilities, coordinates with a Coder+Hacker A2A team to reproduce and implement exploits, then submits findings to earn real money.
- Usage: Use when you want to autonomously discover, validate, and submit high-value security vulnerabilities to bug bounty programs. The agent scans portals (Bugcrowd, HackerOne, bughunters.google.com), ranks by payout, delegates reproduction to the hacker/coder sub-team, and manages the full submission lifecycle.
- Primary Model:
qwen/qwen3-coder-480b-a35b-instruct
Deployment
- Local path:
/Users/jeremy/dev/SIN-Solver/a2a/team-coding/A2A-SIN-BugBounty - GitHub repo:
https://github.com/delqhi/sin-bugbounty - Workforce index:
https://a2a.delqhi.com - Landing page:
https://delqhi-sin-bugbounty.hf.space - Public A2A / CIMD:
https://a2a.delqhi.com/agents/sin-bugbounty - Hugging Face Space:
https://huggingface.co/spaces/delqhi/sin-bugbounty - Hugging Face repo id:
delqhi/sin-bugbounty - Cloudflare tunnel:
sin-bugbounty - Runtime target:
Hugging Face Space free CPU VM
Runtime Shape
- A2A JSON-RPC runtime
- MCP stdio runtime
- CLI wrapper for local and automated use
- publish-ready Docker/Hugging Face Space layout
A2A Surface
- Card:
GET /.well-known/agent-card.json - Alias:
GET /.well-known/agent.json - Health:
GET /health - RPC:
POST /a2a/v1
MCP Surface
- Transport:
stdio - Config:
./mcp-config.json - OpenCode client:
./clients/opencode-mcp.json - Codex client:
./clients/codex-config.toml
Local Commands
sin-bugbounty serve-a2a
sin-bugbounty serve-mcp
sin-bugbounty print-card
sin-bugbounty run-action '{"action":"agent.help"}'
sin-bugbounty run-action '{"action":"sin.bugbounty.health"}'Publication Notes
- This package is Docker/Hugging Face Space ready via the repository
Dockerfile. - The standalone GitHub repo should contain the same contents as this directory root.
- Remote publication is only complete after landing, agent card, and A2A endpoint reachability are verified with the live audit.
