bbsalisted
Install: claude install-skill ShulkwiSEC/bugbounty.sa
# bbsa — bugbounty.sa CLI + MCP
bbsa is a CLI (`bbsa`) and MCP server (`bbsa-mcp`) for bugbounty.sa. Reading is unrestricted. Submitting is two steps: `bbsa reports draft` saves a Markdown file locally, and only `bbsa reports push` sends it.
**Always draft first, and never push unless the user asks you to.** Every report begins as a local draft the user can read. Pushing is a separate, explicit step: run `bbsa reports push` only when the user has asked for that specific draft to be submitted. If they have not asked, hand them the command instead.
Two things enforce this beyond the instruction: the MCP server has **no submit tool** (`draft_report` writes to the user's disk and nothing else), and `bbsa reports push` **refuses to send unless `BBSA_ALLOW_PUSH=1` is set**. Drafting is never gated. A submitted report cannot be edited or withdrawn by a researcher.
Do not set `BBSA_ALLOW_PUSH` yourself, do not add it to the user's shell profile, and do not suggest exporting it. If the user asks you to submit a draft, run it inline for that one command:
```bash
BBSA_ALLOW_PUSH=1 bbsa reports push d1 --agree
```
## When to use
Use when the user wants data from bugbounty.sa: profile, programs, reports, invoices, finance, leaderboard, companies, or notifications; when they want a report drafted for a program; or when they need the token/MCP setup.
**Not for**: editing or deleting platform data, or commenting on reports. The package exposes no such endpoints. Local drafts can be d