Test web and api security
Skill gaelic-ghost/socket/plugins/cybersecurity-skills/skills/test-web-and-api-security
The Source for macOS Agent Workflows
npx -y skills add gaelic-ghost/socket --skill test-web-and-api-securityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Test an explicitly authorized web application or API using current OWASP guidance and bounded manual or automated checks. Use for authentication, authorization, session, input, browser, API schema, business logic, file handling, server-side request, configuration, transport, error, and data-exposure tests when accounts, roles, target, rate, evidence, and stop conditions are defined.
SKILL.md
2.0 KB, as published. Nobody here has run it
Test Web And API Security
Overview
Test one scoped property at a time with role-aware accounts and reproducible requests. Use passive observation before active mutation and review automated scanner behavior before it reaches the target.
Read references/web-api-test-plan.md and current OWASP WSTG/API guidance before execution.
Workflow
- Load the approved scope, environment, accounts/roles, data, rate limits, and stop conditions.
- Map the application.
- Record hosts, routes, APIs/schemas, roles, trust boundaries, sessions/tokens, browser controls, uploads, integrations, and state-changing operations.
- Capture a baseline.
- Preserve normal requests/responses and expected authorization for each role and resource owner.
- Test by security property.
- Cover identity/session, object/function authorization, input handling, browser/client boundaries, server-side fetches, files, configuration, errors, data exposure, business logic, and rate/resource controls as scope permits.
- Use tools deliberately.
- Keep proxy/browser history scoped; review ZAP or Nuclei configuration/templates; exclude destructive or broad checks; record exact versions and requests.
- Validate candidates.
- Reproduce with the smallest request, negative control, different role/owner, and fixed/mitigated state when available.
- Clean up.
- Remove test data/accounts/tokens, restore state, and report anything that could not be reverted.
Output
Return scope/accounts, application map, tests and evidence, validated findings, negative results/coverage gaps, cleanup, and retest criteria.