Authorized Pen Testing
Active security testing needs explicit permission and a defined target. Authorized Pen Testing groups three independent specialist branches so an authorized team can choose the surface that matches the objective without presenting the bundle as one combined offensive-security engine.
What this bundle gives you
- A surface-specific branch for API, web or browser, and identity or privilege objectives.
- Bounded active testing under named scope and explicit authorization.
- Evidence that preserves the tested objective, observed result, limits, and stop conditions.
- Separate specialist paths rather than a claim of one automated offensive-security system.
How the skills fit together
The intended relationship is choose an authorized surface -> test a bounded objective -> preserve the proof. API Penetration Testing, Web Penetration Testing, and Identity Penetration Testing are alternatives or specialist branches. Choose the branch that matches the target and objective. They do not automatically run together and they do not grant permission to test.
Included Skills
- API Penetration Testing: performs authorized active testing of an API surface for a named objective.
- Web Penetration Testing: performs authorized active testing of a web or browser surface for a named objective.
- Identity Penetration Testing: performs authorized active testing of identity or privilege objectives.
Typical Workflows
- Choose API Penetration Testing for a named API contract or behavior objective, with the target and limits documented.
- Choose Web Penetration Testing for a named browser or web-surface objective.
- Choose Identity Penetration Testing for a named privilege, tenant, or authorization-boundary objective.
- Preserve the evidence and pass supported findings to Find, Validate & Fix or Security Controls & Release when remediation or release evidence is separately required.
Who It Is For
Authorized security testers, AppSec teams, and engineering organizations that have permission to test a named surface and need a bounded specialist workflow.
Why Buy the Bundle
The bundle makes the surface choice explicit. Buyers can select the specialist branch that matches the objective while keeping authorization, scope, controlled identities or tokens, limits, and stop conditions visible instead of hiding them behind a generic testing claim.
Boundaries
Bundle ownership does not grant testing authorization. Explicit permission is required, with named targets and scope, controlled identities or tokens where applicable, rate, time, and data limits, prohibited actions, and stop conditions. Destructive or out-of-scope testing is excluded. This is not a promise of a full pentest, automatic testing, comprehensive coverage, vulnerability discovery, attack prevention, or guaranteed security outcomes.
Individual Ownership
This Agensi bundle contains three separate listings. Each included skill remains independently usable, independently owned, and selectable for work that does not require the other skills.
Works with any agent that signs in to Agensi, such as Claude, ChatGPT, Claude Code, Cursor and Codex CLI.
One payment, lifetime access. 3 skills unlock instantly in your library.
What's included
3 skillsAuthorized API pentest that drives toward a real objective, not a checklist
Chain web findings into a proven intrusion, only as far as the objective needs
Prove a privilege or tenant boundary can be crossed minimally, with authorization
See it in action
API Penetration Testing
Example session with this skill installed
Test for IDOR/BOLA on my endpoints
- Read your context and instructions
- Compiled the api penetration testing
EXECUTION CLASSIFICATION
- USER-SUPPLIED FACTS: test objective (IDOR/BOLA).
- OBSERVED EVIDENCE: none.
- HYPOTHETICAL / EXAMPLES: candidate REST API endpoints below are marked [HYPOTHETICAL EXAMPLE].
- UNVERIFIED / MISSING INPUTS: authorization statement, target service URL, environment, test identities/tokens, scope limits.
EXECUTION MODE: NONE — BLOCKED
ENGAGEMENT
- AUTHORIZATION: MISSING / NOT SUPPLIED (Active testing blocked)
- TARGETS: NOT SUPPLIED
- ENVIRONMENT: UNVERIFIED / NOT SUPPLIED
- SCOPE: NOT SUPPLIED
EVIDENCE STATUS: BLOCKED — MISSING AUTHORIZATION/SCOPE
CONFIRMED HTTP FINDING: NO
OBSERVED: NONE — NO ACTIVE RUNTIME EXECUTION PERFORMED
ANALYSIS & HYPOTHETICAL TEST PLAN:
Active testing cannot proceed without explicit authorization, target URL, and scoping boundaries.
Below is an illustrative test structure for when authorization and scope are provided:
[HYPOTHETICAL EXAMPLE TEST CASE]
- Target: [HYPOTHETICAL] https://target-api.local/api/v1/resources/{id}
- Identities needed: [HYPOTHETICAL] User A (owner), User B (non-owner)
- Step 1 (Planned Baseline): User A requests owned resource -> expected 200
- Step 2 (Planned BOLA probe): User B requests User A's resource -> expected 403/404
LIMITATIONS: No runtime commands executed. No responses observed. No fabricated status codes generated.
NEXT STEPS: Provide written authorization, target endpoint/environment, and valid test accounts.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads these skills and uses them on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every skill in this bundle goes through our trust checks.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.