Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

pentest-exploit-execution-payload-control

Étoiles2

Forks0

Mis à jour3 juillet 2026 à 09:18

Deterministic exploit execution and payload control from validated primitives. Use for exploit implementation, payload hardening, chaining confirmed weaknesses, post-exploitation proof, controlled impact demonstration, reliability notes, and rollback or containment planning.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

crtvrffnrt

crtvrffnrt/skills

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en sécurité de l'informationProfessions informatiques et mathématiques·SOC 15-1212

SKILL.md

readonly

name	pentest-exploit-execution-payload-control
description	Deterministic exploit execution and payload control from validated primitives. Use for exploit implementation, payload hardening, chaining confirmed weaknesses, post-exploitation proof, controlled impact demonstration, reliability notes, and rollback or containment planning.

Exploit Execution & Payload Control

Use When

A validated primitive exists and the next phase is controlled exploit implementation, payload hardening, chaining, reliability testing, or impact proof.
The task is explicitly a lab exploit-development exercise with clear boundaries.

Handoff Criteria

Hand off to CVE, input/protocol, authz, XSS, OOB, or business-logic workflows when the primitive is not yet validated.
Hand off to reporting when impact proof and reproducibility are complete.

Output Schema

Exploit plan: preconditions, primitive, payload strategy, safety guardrails
Execution log: step, result, evidence
Final capability statement: what attacker can do after exploitation

Instructions

Require at least one validated security primitive before exploit implementation.
Choose deterministic payloads with clear rollback or containment strategy.
Execute in smallest viable sequence to prove impact with minimal disruption.
Record exact preconditions and environmental dependencies.
Separate exploit reliability issues from vulnerability existence.
Produce reproducible commands and evidence suitable for independent verification.

Verification Gate

Prefer deterministic, low-noise payloads over broad spray strategies.
Preserve proof artifacts that map directly to attacker capability.
Stop when impact is proven; avoid unnecessary escalation.
Claim successful exploitation only from direct capability evidence, not partial side effects.
Run destructive payloads only when explicitly authorized.
Check tool status and dependencies before relying on them; if unavailable, use the safest fallback and report the gap.

Plus depuis ce dépôt

même dépôt

pentest-shodan-helper

crtvrffnrt/skills

Shodan CLI-only search workflow for query design, filter selection, count/stats validation, and search-result retrieval through /root/.local/bin/shodan.

2026-07-082

pentest-cve-reverse-engineer

crtvrffnrt/skills

Manual vulnerability research skill for finding advisories, downloading affected and fixed artifacts, diffing patches, confirming root cause, and writing reliable reports across products and technologies.

2026-07-082

pentest-gemini-sub-htb

crtvrffnrt/skills

Controlled lab skill for Hack The Box, CTF, and private lab workflows from reconnaissance, enumeration, vulnerability research, exploitation, foothold, and privilege escalation through evidence consolidation.

2026-07-032

incident-response-fileanalyser

crtvrffnrt/skills

Static malware reverse-engineering and threat-intelligence triage for unknown files, Windows EXE/PE binaries, scripts, archives, ISOs, JavaScript, PowerShell, documents, and unpacked payloads. Use when a user provides a sample path, hash, filename, or file and asks whether it is malicious, benign, suspicious, contains IoCs, or should be reverse engineered with Ghidra, strings, capa, YARA, public TI, and structured phase artifacts.

2026-07-032

incident-response-bec

crtvrffnrt/skills

BEC and AiTM incident-response skill for suspicious sign-ins, mailbox abuse, forwarding, inbox rules, session theft, token replay, consent abuse, and secondary phishing.

2026-07-032

incident-response-main

crtvrffnrt/skills

Defensive incident-response companion for Microsoft Entra ID, Microsoft 365, Defender, and mixed identity or endpoint incidents. Use for sign-in triage, public-IP enrichment, initial scoping, containment planning, and analyst-ready notes.

2026-07-032

name	pentest-exploit-execution-payload-control
description	Deterministic exploit execution and payload control from validated primitives. Use for exploit implementation, payload hardening, chaining confirmed weaknesses, post-exploitation proof, controlled impact demonstration, reliability notes, and rollback or containment planning.

Exploit Execution & Payload Control

Use When

A validated primitive exists and the next phase is controlled exploit implementation, payload hardening, chaining, reliability testing, or impact proof.
The task is explicitly a lab exploit-development exercise with clear boundaries.

Handoff Criteria

Hand off to CVE, input/protocol, authz, XSS, OOB, or business-logic workflows when the primitive is not yet validated.
Hand off to reporting when impact proof and reproducibility are complete.

Output Schema

Exploit plan: preconditions, primitive, payload strategy, safety guardrails
Execution log: step, result, evidence
Final capability statement: what attacker can do after exploitation

Instructions

Require at least one validated security primitive before exploit implementation.
Choose deterministic payloads with clear rollback or containment strategy.
Execute in smallest viable sequence to prove impact with minimal disruption.
Record exact preconditions and environmental dependencies.
Separate exploit reliability issues from vulnerability existence.
Produce reproducible commands and evidence suitable for independent verification.

Verification Gate

Prefer deterministic, low-noise payloads over broad spray strategies.
Preserve proof artifacts that map directly to attacker capability.
Stop when impact is proven; avoid unnecessary escalation.
Claim successful exploitation only from direct capability evidence, not partial side effects.
Run destructive payloads only when explicitly authorized.
Check tool status and dependencies before relying on them; if unavailable, use the safest fallback and report the gap.