Borrowing it
Nothing to install: this file belongs to Suzu-Testing/metasploit-cursor-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Suzu-Testing/metasploit-cursor-harness/main/.cursor/skills/snmp-pentest/SKILL.mdgit clone --depth 1 https://github.com/Suzu-Testing/metasploit-cursor-harnessWrote 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.
[](https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/snmp-pentest)<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/snmp-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/snmp-pentest/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.
<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/snmp-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/snmp-pentest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00034 | $0.02134 |
| Opus 5 | $0.00017 | $0.01067 |
| Sonnet 5 | $0.00007 | $0.00427 |
| Haiku 4.5 | $0.00003 | $0.00213 |
Grade B, and why
snmp-pentest scanned grade B 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 9d 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.
Harvests environment variablesmediumData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
- Harvest credentials from process lists, config OIDs, routing data Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SNMP Pentest
Prerequisites
- Target is in scope (
scope/scope-master.txt, engagement ROE).
Ports and detection
| Port | Service |
|---|---|
| 161/udp | SNMP agent queries |
| 162/udp | SNMP traps (outbound) |
| 10161/udp | SNMP over TLS (when present) |
Service discovery
MSF MCP (preferred):
msf_run_auxiliary_module(
module_name="auxiliary/scanner/snmp/snmp_login",
engagement_id="<id>",
options={"RHOSTS": "<target>", "RPORT": 161, "COMMUNITY": "public", "THREADS": 5}
)
CLI fallback:
nmap -sU -p161 --script "snmp* and not snmp-brute" <target>
onesixtyone -c community.txt <target>
snmp-check <target> -c public
Workflow
Task Progress:
- [ ] Community string brute force
- [ ] SNMPv3 auth brute
- [ ] MIB walk and OID enumeration
- [ ] Config and credential disclosure
- [ ] Write access / Net-SNMP extend RCE
- [ ] Document findings
Community string brute force (v1/v2c)
MSF MCP (preferred):
msf_run_auxiliary_module(
module_name="auxiliary/scanner/snmp/snmp_login",
engagement_id="<id>",
options={
"RHOSTS": "<target>",
"RPORT": 161,
"COMMUNITY": "public",
"PASS_FILE": "/usr/share/wordlists/snmp-default.txt",
"THREADS": 10
}
)
CLI fallback:
onesixtyone -c community.txt <target>
onesixtyone -i targets.txt -c community.txt
hydra -P community.txt -v <target> snmp
nmap -sU -p161 --script snmp-brute <target>
Default strings: public (read), private (read/write).
SNMPv3 auth brute
MSF MCP (preferred):
msf_run_auxiliary_module(
module_name="auxiliary/scanner/snmp/snmp_login",
engagement_id="<id>",
options={
"RHOSTS": "<target>",
"RPORT": 161,
"VERSION": "3",
"USERNAME": "admin",
"PASSWORD": "password",
"AUTH_PROTOCOL": "SHA",
"PRIV_PROTOCOL": "AES",
"THREADS": 5
}
)
CLI fallback:
# Enumerate SNMPv3 engine ID and users
nmap -sU -p161 --script snmp-info <target>
# Brute auth/priv
onesixtyone -c community.txt <target> # v1/v2c first
snmpwalk -v3 -l authNoPriv -u admin -a SHA -A password <target>
snmpwalk -v3 -l authPriv -u admin -a SHA -A password -x AES -X privpass <target>
# Hydra SNMPv3
hydra -P passwords.txt -v <target> snmp -m ":admin:SHA:"
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.
- 9d ago First seen · 236 lines · 34 tokens per session scan B 8a1e4d2ed1e2
snmp-pentest is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 15d ago), licensed MIT. It adds 34 tokens to every session and 2,134 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…