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.
npx agentmods add skills/s0ld13rr/pentestcode/mailnpx skills add s0ld13rr/pentestcode --skill mailgit clone --depth 1 https://github.com/s0ld13rr/pentestcodeWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00078 | $0.00549 |
| Opus 5 | $0.00039 | $0.00275 |
| Sonnet 5 | $0.00016 | $0.00110 |
| Haiku 4.5 | $0.00008 | $0.00055 |
Grade A, and why
svc-mail scanned grade A with 0 findings 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 2d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Mail Server Attack Reference
SMTP (25/465/587)
# Banner grab and commands
nc -nv <target> 25
nmap --script smtp-commands,smtp-enum-users,smtp-open-relay -p 25 <target>
# User enumeration via VRFY
telnet <target> 25
VRFY root
VRFY admin
VRFY <username>
# User enumeration via RCPT TO
EHLO test
MAIL FROM:<[email protected]>
RCPT TO:<admin@<domain>> # 250 = exists, 550 = doesn't
# Automated user enumeration
smtp-user-enum -M VRFY -U /usr/share/seclists/Usernames/Names/names.txt -t <target>
smtp-user-enum -M RCPT -U users.txt -D <domain> -t <target>
Open Relay
# Test relay
telnet <target> 25
EHLO test
MAIL FROM:<[email protected]>
RCPT TO:<[email protected]>
DATA
Subject: Relay Test
Relay test body
.
QUIT
# Nmap check
nmap --script smtp-open-relay -p 25 <target>
POP3 (110/995) & IMAP (143/993)
# Banner grab
nc -nv <target> 110
nc -nv <target> 143
# POP3 brute force
hydra -l <user> -P wordlist.txt pop3://<target>
# IMAP brute force
hydra -l <user> -P wordlist.txt imap://<target>
# If authenticated (POP3)
USER <username>
PASS <password>
LIST
RETR 1
# If authenticated (IMAP)
a1 LOGIN <user> <password>
a2 LIST "" "*"
a3 SELECT INBOX
a4 FETCH 1 BODY[]
Webmail
- OWA (Outlook Web Access):
/owa/,/ecp/— brute force, spray - Roundcube: check version for known CVEs
- SquirrelMail:
/squirrelmail/— old versions have RCE
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.
- 2d ago First seen · 76 lines · 78 tokens per session scan A 585484b36aaa
svc-mail is a skill published in the GitHub repository s0ld13rr/pentestcode (566 stars, last pushed 11d ago), licensed MIT. It adds 78 tokens to every session and 549 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
stripe-projects
Use after E2B sandbox/API access has been provisioned through Stripe Projects and the user needs to use the resulting E2B API key with the E2B CLI, JavaScript SDK, Python SDK, or Code Interpreter SDK.
greeting-user
Explains how to properly greet the user.
using-process-tool
Describes how to correctly use 'process' tool.
test-skill
test description.
documents
Create, read, edit, review, comment on, sanitize, render, and validate Microsoft Word DOCX documents. Use whenever a DOCX or Word document is a primary input or deliverable, including reports, proposals, forms, templates, tracked revisions, comments, tables, images, headers, footers, and style-preserving edits.
Read, create, inspect, merge, split, rotate, encrypt, fill, and validate PDF files. Use when the user asks to work with a PDF or convert supported Markdown into a polished PDF in AstrBot.