agentsclimarketplace

Scope authorized security test

Skill gaelic-ghost/socket/plugins/cybersecurity-skills/skills/scope-authorized-security-test

The Source for macOS Agent Workflows

Install
npx -y skills add gaelic-ghost/socket --skill scope-authorized-security-test

Assembled 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

Define and verify authorization, targets, rules of engagement, data handling, safety controls, and stop conditions before active security testing. Use for penetration tests, vulnerability scans, exploit validation, web/API tests, network probing, red-team-like exercises, bug bounty work, or agent-driven testing where ownership and allowed techniques must be explicit.

SKILL.md

2.3 KB, 375 tokens by cl100k_base, as published. Nobody here has run it

Scope Authorized Security Test

Overview

Turn permission into an executable scope record before sending active traffic or running a proof of concept. Authorization must identify the owner and boundaries; access to a target or a public address is not permission.

Read references/active-test-scope.md and complete every applicable field.

Workflow

  1. Identify authority.
    • Record target owner, authorizing person/record, tester, contacts, dates, jurisdiction or program policy, and evidence of permission.
  2. Resolve targets precisely.
    • List domains, hosts, addresses/ranges, applications, APIs, repositories, accounts, environments, and third-party dependencies.
    • List exclusions explicitly and define how dynamic/cloud/CDN targets are resolved.
  3. Define allowed techniques.
    • Separate passive review, discovery, authenticated testing, automated scanning, fuzzing, exploit validation, social/physical testing, persistence, credential access, data access, and denial-of-service.
    • Default unlisted techniques to disallowed.
  4. Set operational controls.
    • Define source addresses, accounts, rate/concurrency, time windows, test data, logging, notification, emergency stop, cleanup, and restoration.
  5. Define data handling.
    • Minimize accessed data; specify retention, encryption, screenshots/logs, secrets, evidence transfer, disclosure, and deletion.
  6. Establish stop conditions.
    • Stop on target drift, third-party impact, instability, sensitive data beyond minimum proof, unexpected privileges, scope ambiguity, or an unapproved technique.
  7. Approve the test plan.
    • Show exact targets and effects before tools run; update the scope record before expanding work.

Output

Return authority, included/excluded targets, allowed/disallowed techniques, operational controls, data handling, stop/escalation contacts, and approval state.

What ships with it: 2 files

990 B alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.