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/linux-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/linux-pentest)<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/linux-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/linux-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/linux-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/linux-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.00039 | $0.02103 |
| Opus 5.5 | $0.00016 | $0.00841 |
| Sonnet 5.5 | $0.00008 | $0.00421 |
| Haiku 4.5 | $0.00004 | $0.00210 |
Grade B, and why
linux-pentest scanned grade B with 2 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 1mo 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo vim -c ':!/bin/sh' Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Reaches for credential filesmediumPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
echo "ssh-rsa AAAA..." >> ~/.ssh/authorized_keys 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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linux Pentest
Prerequisites
- Linux targets or sessions are in scope.
- Container context: also load
container-devops-pentest. - Service attacks (SSH, FTP): load
hacktricks-methodologyor dedicated service skills.
Workflow
Task Progress:
- [ ] Enumerate OS, kernel, user, groups, sudo, cron, capabilities
- [ ] Run privesc checklist (SUID, writable paths, PATH, LD_PRELOAD)
- [ ] Check container breakout indicators if on Docker/K8s host
- [ ] Document escalation path and evidence
Phase 1: Enumeration
System info
MSF MCP (preferred):
msf_run_post_module(
module_name="post/linux/gather/enum_system",
engagement_id="<id>",
session_id=<sid>,
options={}
)
msf_run_post_module(
module_name="post/linux/gather/enum_users_history",
engagement_id="<id>",
session_id=<sid>,
options={}
)
msf_run_post_module(
module_name="post/linux/gather/checkcontainer",
engagement_id="<id>",
session_id=<sid>,
options={}
)
CLI fallback:
cat /etc/os-release
uname -a
id
sudo -l
Automated: LinPEAS, LinEnum, linux-exploit-suggester, pspy.
SUID and capabilities
MSF MCP (preferred):
msf_run_post_module(
module_name="post/linux/gather/enum_configs",
engagement_id="<id>",
session_id=<sid>,
options={}
)
CLI fallback:
find / -perm -4000 -type f 2>/dev/null
find / -perm -2000 -type f 2>/dev/null
getcap -r / 2>/dev/null
Common abusable: find, vim, python, pkexec, doas. Check GTFOBins.
Cron and systemd
MSF MCP (preferred):
msf_run_post_module(
module_name="post/linux/gather/enum_network",
engagement_id="<id>",
session_id=<sid>,
options={}
)
General OS/kernel context is covered by post/linux/gather/enum_system in Phase 1; use enum_network here for scheduled-task and service reachability context.
CLI fallback:
cat /etc/crontab
ls -la /etc/cron.*
systemctl list-timers
systemctl list-unit-files --type=service
grep -r ExecStart /etc/systemd/system/ /lib/systemd/system/ 2>/dev/null
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.
- 1mo ago First seen · 361 lines · 39 tokens per session scan B 925593abd6aa
linux-pentest is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 2,103 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…