agentsclimarketplace

Pentest redteam ops

Skill 0x-Professor/Agent-Skills-Hub/skills/pentest-redteam-ops

Public skill pack for AI coding/automation/penetration-testing agents.

Install
npx -y skills add 0x-Professor/Agent-Skills-Hub --skill pentest-redteam-ops

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

  • 10 stars10 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

Coordinate autonomous pentest skills with dependency enforcement, deconfliction, and emergency stop controls.

SKILL.md

1.3 KB, 286 tokens by cl100k_base, as published. Nobody here has run it

Pentest Red Team Ops

Stage

  • PTES: all
  • MITRE: Full ATT&CK chain

Objective

Run full engagement sequencing and produce timeline and status dashboards.

Required Workflow

  1. Validate scope before any active action and reject out-of-scope targets.
  2. Run only authorized checks aligned to PTES, OWASP WSTG, NIST SP 800-115, and MITRE ATT&CK.
  3. Write findings in canonical finding_schema format with reproducible PoC notes.
  4. Honor dry-run mode and require explicit --i-have-authorization for live execution.
  5. Export deterministic artifacts for downstream skill consumption.

Execution

python skills/pentest-redteam-ops/scripts/redteam_ops.py --scope scope.json --target <target> --input <path> --output <path> --format json --dry-run

Outputs

  • engagement-log.json
  • redteam-timeline.json
  • orchestration-report.json

References

  • references/tools.md
  • skills/autonomous-pentester/shared/scope_schema.json
  • skills/autonomous-pentester/shared/finding_schema.json

Legal and Ethical Notice

WARNING AUTHORIZED USE ONLY
This skill executes real security testing tools against live targets.
Use only with written authorization.

What ships with it: 4 files

4.3 KB alongside SKILL.md, 1 of them executable

agents/

assets/

references/

scripts/

Gives 0 of the 12 instructions most ship operate skills give in 286 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

  • Document a rollback plan before deploymentin 41 of 779, across 22 files
  • Update the changelogin 21 of 779, across 19 files
  • Run the test suitein 20 of 779
  • Create an annotated git tagin 20 of 779
  • Clean up feature flags after full rolloutin 18 of 779, across 10 files
  • Verify deployment health after launchin 18 of 779, across 10 files
  • Test both feature flag statesin 17 of 779, across 9 files
  • Verify the working tree is cleanin 17 of 779
  • Make database migrations backward-compatiblein 16 of 779, across 8 files
  • Set up error monitoring before launchin 15 of 779, across 7 files
  • Monitor metrics at each rollout stagein 14 of 779, across 5 files
  • Create a GitHub releasein 14 of 779

Said here and by no other author read

  • validate scope before any active action
  • reject out-of-scope targets
  • write findings in canonical finding schema format
  • include reproducible proof of concept notes
  • honor dry-run mode
  • require explicit authorization flag for live execution

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. 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.