Security
Continuous Pentester
Continuous Pentester
Start with Authorized app or staging URL + scope. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.
- 1/wkEvidence reports
FactoriesStart with your sources
IdleIllustrative runMissing authHigh severity
- Request
- GET /api/invoices/inv_1042
- Response
- 200 OK
Evidence for the pull request200 OK
GET /api/invoices/inv_1042
- Confirmed findings
- 0
- Draft pull requests
- 0
Draft pull requestfix/invoice-session-checkmain
Require a session on GET /api/invoices/[id]
Related solutions
See how teams in this category put agents to work.
Integrations
0 integrationsGet started with Continuous Pentester
Pick an example, connect your tools, and review the first run.
Set up the Continuous Pentester agent template for this project. Follow /SKILL.md for the exact CLI commands.
Goal: Investigate exposed surfaces within the permitted scope, reproduce confirmed findings, and retest fixes. Begin with public, non-destructive checks; authenticated coverage needs test access.
1. Install the CLI if it is not on PATH, check that I am signed in, and select my team and project.
2. List the first-party workflow templates. If `continuous-pentester` is listed, instantiate it with `--path.slug continuous-pentester` and start the run; otherwise create a project from this template at /new?template=continuous-pentester&preset=trial.
3. Share the run id, follow the run until it finishes, and summarize its outputs and changes.
Ask me before spending FTAI or changing anything outside this repository.
Launch from Claude Code, Codex, Cursor, and other agents.