القائمة
Entry point for the Arsenal automated attack pipeline. Cron-triggered daily scan of lab targets. Chains through recon → skill-match → execute → report → notify.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Arsenal offensive security agent — 5-phase attack workflow. When a user asks to attack, hack, pentest, or assess a target, follow this skill. 764 cybersecurity skills, 22 lab targets, real recon tools (nmap, dig, curl, openssl).
Phase 3 — Execution. Run matched exploit playbooks against lab targets. Triggered by arsenal-phase-skill-match when SKILLS_MATCHED is found.
Phase 5 — Notification. Deliver pipeline results via Telegram message. Terminal link for any phase — starter failure, recon no-targets, execution critical findings, or final report.
Phase 1 — Reconnaissance. Run nmap, dig, curl, openssl against lab targets. Triggered by arsenal-pipeline-starter when TARGETS_READY is found.
Phase 4 — Report. Compile execution findings into a structured markdown report. Triggered by arsenal-phase-execute when EXECUTION_COMPLETE is found.
Phase 2 — Skill Selection. Map recon findings to specific exploit skills from the 764-skill catalog. Triggered by arsenal-phase-recon when RECON_COMPLETE is found.
استنادا إلى تصنيف SOC المهني
| name | arsenal-pipeline-starter |
| description | Entry point for the Arsenal automated attack pipeline. Cron-triggered daily scan of lab targets. Chains through recon → skill-match → execute → report → notify. |
This is the scheduled entry point for the automated Arsenal attack pipeline. Invoked by cron daily at 3am UTC, or manually when the user says "scan the lab."
First, list available lab targets:
arsenal_lab_targets() to see all Docker and Proxmox targetsFor Docker targets that might be running, check their status:
docker ps --format "{{.Names}}" 2>/dev/null || echo "no docker" in terminalIf no targets are running, select one Docker target to deploy and scan:
arsenal lab start dvwa via terminal (node dist/index.js lab start dvwa --detach)For any Proxmox LXC targets, note that they must be already deployed and running
Produce a summary of targets ready for scanning:
When finished, pass a target summary to the next phase. Output must contain:
TARGETS_READY: target1|IP:port|type, target2|IP:port|type
Example:
TARGETS_READY: dvwa|172.17.0.2:80|docker, proxmox-sqli|192.168.8.60:80|lxc
on_complete: