mks

mks is a skill for Claude Code from Stickman230/claude-pentest. It costs 54 tokens per session (2,530 once invoked), scanned A, original, MIT.

A guide for using an MKS, or Metasploit-Kali Server, to run Kali security tools through web requests when that server is configured.

In plain words
What is it for?
Connecting security workflows to MKS, probing tool support, calling tools through the server's REST endpoints, interpreting responses, and choosing local commands when MKS is unavailable.
Why use it?
It checks whether the server is available and usable, then defines how to handle requests, responses, errors, and fallback to local commands.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the pentest plugin — 7 skills, 5 commands, 15 agents shipped together

Good fit Connecting security workflows to MKS, probing tool support, calling tools through the server's REST endpoints, interpreting responses, and choosing local commands when MKS is unavailable.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stickman230/claude-pentest/mks
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Stickman230/claude-pentest --skill mks
Clone the repo
git clone --depth 1 https://github.com/Stickman230/claude-pentest

Made for: Claude Code.

Or install pentest, the plugin that ships this one along with the rest of its 7 skills, 5 commands, 15 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mks

README.md
[![agentmods](https://agentmods.dev/badge/skills/stickman230/claude-pentest/mks/github.svg)](https://agentmods.dev/skills/stickman230/claude-pentest/mks)
Your own site
<a href="https://agentmods.dev/skills/stickman230/claude-pentest/mks"><img src="https://agentmods.dev/badge/skills/stickman230/claude-pentest/mks/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mks

Your own site · 80×15
<a href="https://agentmods.dev/skills/stickman230/claude-pentest/mks"><img src="https://agentmods.dev/badge/skills/stickman230/claude-pentest/mks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,530 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.02530
Opus 5 $0.00027 $0.01265
Sonnet 5 $0.00011 $0.00506
Haiku 4.5 $0.00005 $0.00253

Measured 10d ago against content hash 67ad60a3d4cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

mks scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

PROBE=$(curl -s -m 20 -X POST "$MKS_URL/api/tools/nmap" \
plugins/pentest/skills/mks/SKILL.md · 225 lines

How it starts

The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MKS — Kali Tool Server Preference

Step 0: Resolve MKS URL

Run once at phase start and store as MKS_URL:

MKS_URL=$(cat .pentest-mks.json 2>/dev/null | jq -r '.url // empty')
  • Non-empty: MKS is active — use the REST endpoints below instead of local Bash tool invocations.
  • Empty: MKS not configured — skip all MKS calls and use local Bash commands as documented in the agent workflow.

Step 0.5: Capability probe (do this once before the first tool call)

Some server builds have a defect where the structured /api/tools/* endpoints (and /health) crash when the command is constructed as an argv list — every structured tool call returns an error like CommandExecutor expects a string, but got list, and the tools appear unusable even though they are installed. The generic POST /api/command endpoint (raw command string) is unaffected.

Probe once and set MKS_TOOLS_MODE:

PROBE=$(curl -s -m 20 -X POST "$MKS_URL/api/tools/nmap" \
  -H "Content-Type: application/json" \
  -d "{\"target\":\"127.0.0.1\",\"scan_type\":\"-sn\",\"additional_args\":\"-Pn\"}")
if echo "$PROBE" | grep -qiE 'got list|expects a string|TypeError|Internal Server Error|got a list'; then
  MKS_TOOLS_MODE="command"   # structured endpoints are broken on this server → route via /api/command
else
  MKS_TOOLS_MODE="structured" # structured endpoints work → use /api/tools/* as documented
fi
  • MKS_TOOLS_MODE="structured" → use the /api/tools/{tool} endpoints in the Endpoints section.
  • MKS_TOOLS_MODE="command" → use the /api/command fallback (see that section) for every tool.

Log the result: {"action":"mks-capability-probe","tools_mode":"<structured|command>"}.

Security note for command mode: /api/command runs the string in a shell (shell=True-style), so it is injection-prone if any target/argument is attacker-controlled. In a pentest the target and args are operator-controlled against the operator's own Kali host, so this is an acceptable bridge — but never interpolate untrusted scan output back into an /api/command string. The structured endpoints are the safer design; prefer them whenever the probe says they work.

Read the full file on GitHub · 225 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 225 lines · 54 tokens per session scan A 67ad60a3d4cf

Subscribe to this mod's changes

mks is a skill published in the GitHub repository Stickman230/claude-pentest (100 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 2,530 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

api-security-testing

Security-test a REST, GraphQL, or gRPC API with Strix — autonomous agents that enumerate endpoints from an OpenAPI/GraphQL schema (or by crawling), then actually exploit the API-specific vulnerability classes in the OWASP API Security Top 10 (2023) — broken object-level authorization (BOLA/IDOR), broken object…

usestrix/strix · 144 tokens

fix-security-vulnerabilities-with-strix

Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use…

usestrix/strix · 124 tokens

owasp-top-10-testing

Test an application against the OWASP Top 10 with Strix — autonomous AI agents that attempt real exploits for each category of the current OWASP Top 10:2025 (broken access control including SSRF, security misconfiguration, software supply chain failures, cryptographic failures, injection, insecure design…

usestrix/strix · 151 tokens

find-security-vulnerabilities-in-code

Find security vulnerabilities in a codebase or repository with Strix — a white-box AI security review that reads your source, reasons about the actual data flow and authorization model, then exploits what it finds in a live sandbox so every reported issue has a working proof-of-concept instead of a noisy…

usestrix/strix · 129 tokens

web-app-penetration-testing

Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature…

usestrix/strix · 129 tokens

managed-pentesting-with-strix

Run a managed pentest of a web app, API, repository, or local workspace on the app.strix.ai platform with the strix cloud CLI or REST API — no local Docker or LLM key needed. Safely review and upload local source, register assets, launch and poll scans, triage vulnerabilities, export SARIF, download compliance…

usestrix/strix · 114 tokens