Individual skill

darkmoon-pentest

Use when the user wants to start or follow an autonomous penetration test with their own Darkmoon Pro instance, check the status of a Darkmoon run, list Darkmoon campaigns, or read and triage the findings of a campaign. Requires the darkmoon MCP server and an authorized target.

plugins/ASCIT31/darkmoon-mcp-server/plugins/darkmoon/skills/darkmoon-pentest/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,537
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Darkmoon pentest runs

The `darkmoon` MCP server talks to the Dashboard API of a self-hosted Darkmoon Pro instance
(`DARKMOON_BASE_URL`). The Darkmoon engine and CLI are open source (GPL-3.0), but this server
needs the Pro dashboard; it does not work against the CLI alone.

## Authorization first

Only start a run against a host, URL or scope that the user owns or is explicitly authorized in
writing to test. If authorization is not stated, ask before calling `run_pentest`. Never widen
the target beyond what the user named.

## Workflow