Works with the AI Agents you already use
Security Testing 1
Generate OWASP-aligned security test scenarios and matrices for web/mobile apps and APIs.
$15
security-testing
Example session with this skill installed
Generate a security test matrix for a Node.js API with a profile update endpoint (PATCH /user/:id) using JWT auth. Focus on IDOR and mass assignment.
- Read your context and instructions
- Compiled the security-testing
I have mapped the assets and entry points for the profile update endpoint. Based on the Node.js and JWT stack, I have designed the following non-destructive test scenarios focusing on authorization and data integrity.
Security Test Matrix: Profile Update API
| ID | Threat/Control | Asset/Entry Point | Preconditions | Safe Steps | Expected Control | Risk |
|---|---|---|---|---|---|---|
| SEC-01 | IDOR (Broken Object Level Auth) | PATCH /user/:id | Two active test accounts (User A, User B) | Authenticate as User A; Attempt to PATCH User B's ID with synthetic data | 403 Forbidden or 401 Unauthorized | High |
| SEC-02 | Mass Assignment | PATCH /user/:id | One active test account | Attempt to update "role" or "permissions" field to "admin" in JSON payload | Ignore restricted fields or return 400 Bad Request | Medium |
| SEC-03 | JWT Token Manipulation | PATCH /user/:id | One active test account | Modify JWT payload (e.g., sub/id) without resigning; send request | 401 Unauthorized (Signature verification failure) | High |
| SEC-04 | Input Validation (NoSQL Injection) | PATCH /user/:id | One active test account | Use object-based injection payload in "bio" field (e.g., {"$ne": null}) | Sanitize input or treat as literal string | Medium |
Next steps
1.
Confirm Authorization: Ensure you have written permission to run these tests against the target staging environment.
2. Prepare Fixtures: Create two distinct test users in your database to verify the IDOR scenarios.
3. Execute Safely: Run the tests using a tool like Postman or cURL and capture the response headers for evidence.
Connects securely to your tools. The creator never sees your data.
About this skill
Security testing for modern web and mobile applications is often an afterthought or limited to generic automated scans that miss business logic flaws. This skill provides a structured framework for designing and reviewing authorized, application-specific security tests aligned with OWASP standards.
What it does
- Threat modeling identifies assets, trust boundaries, and entry points based on your specific architecture and tech stack.
- Scenario generation produces non-destructive test cases covering injection, IDOR, XSS, CSRF, and authentication bypass.
- Test matrix creation builds detailed plans including preconditions, safe steps, expected defensive behavior, and cleanup procedures.
- Finding validation distinguishes between automated tool alerts and confirmed issues with realistic impact assessments.
- Remediation guidance recommends minimal code changes and safe retesting protocols for identified vulnerabilities.
How it works
- Map the attack surface by analyzing supplied architecture, roles, and data classes to identify relevant threats.
- Select test vectors from OWASP-aligned categories like input handling, session management, and object-level authorization.
- Define safe execution steps for each scenario, ensuring tests use non-destructive payloads and synthetic data.
- Evaluate and document potential findings by citing exact endpoints, redact secrets, and assign risk ratings.
Frameworks & tools
Works with any web or mobile stack, specifically referencing OWASP WSTG and Top 10. Supports testing for React, Express, PostgreSQL, JWT-based auth, and REST/GraphQL APIs.
Why this beats prompting it yourself
Generic prompts often result in destructive exploit suggestions or vague "check for XSS" advice. This skill enforces a strict safety protocol, requiring explicit authorization and focusing on business logic vulnerabilities like IDOR that scanners typically miss.
Use cases
- Generate OWASP-aligned security scenarios for a new API feature before release.
- Review a file upload implementation for type, size, and content validation flaws.
- Design test cases to verify object-level authorization (IDOR) across multi-tenant environments.
- Audit JWT and cookie-based session management for fixation or bypass risks.
Known limitations
Does not provide compliance attestations or authorize live exploits without written permission. Guidance for regulatory topics is high-level only.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.
Requires explicit authorization before active tests. No automated exploit execution. Regulatory guidance is high-level. Readiness score below 75/100 requires user clarification.
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 this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
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.
Trust & safety
Security scan
Security scan passed 2 days ago