ssh-penetration-testing
Audit SSH Security Safely
SSH assessments can miss weak configuration, exposed keys, and tunnel risks. This skill structures authorized reviews with discovery, audit steps, and report-ready findings.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "ssh-penetration-testing" from https://skillstore.io/skills/sickn33-ssh-penetration-testing.md and its manifest at https://skillstore.io/api/skills/sickn33-ssh-penetration-testing/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "ssh-penetration-testing". Assess this SSH audit summary: OpenSSH 7.2, SHA1 MACs, password authentication enabled.
Expected outcome:
Findings: outdated OpenSSH requires patch review, SHA1 MACs should be disabled, and password authentication needs compensating controls.
Using "ssh-penetration-testing". Prepare a test plan for an authorized internal SSH review.
Expected outcome:
Plan: confirm scope, discover services, review configuration, check key exposure, protect evidence, and map each finding to remediation.
Using "ssh-penetration-testing". Summarize SSH tunnel risk for a change board.
Expected outcome:
Risk summary: Local, remote, and dynamic forwarding can bypass segmentation. Disable unused forwarding and monitor approved exceptions.
Security Audit
CriticalThe skill is highly dual-use and includes credential attacks, SSH key discovery, Metasploit usage, tunneling, pivoting, and post-exploitation actions. Markdown backtick detections and placeholder private IP findings were dismissed where they were only formatting or example targets. Confirmed findings show unacceptable risk for unsupervised marketplace publishing without major safety restructuring.
Confirmed security concerns (55)
Show all 55 confirmed findings
Capability review items (42)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (46)
🌐 Network access (50)
📁 Filesystem access (28)
Detected Patterns
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-ssh-penetration-testing/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-ssh-penetration-testing?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-ssh-penetration-testing?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-ssh-penetration-testing/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-ssh-penetration-testing.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). ssh-penetration-testing security audit report (audit version 5) [Author version 1.1]. Skillstore. https://skillstore.io/skills/sickn33-ssh-penetration-testing/audits/5BibTeX citation
@techreport{sickn33-sickn33-ssh-penetration-testing-2026,
author = {sickn33},
title = {ssh-penetration-testing security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-ssh-penetration-testing/audits/5},
note = {Author version 1.1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "ssh-penetration-testing security audit report (audit version 5)"
version: "1.1"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/sickn33-ssh-penetration-testing/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-ssh-penetration-testing:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Prepare an SSH assessment plan
Create a scoped workflow for authorized SSH discovery, configuration review, and evidence collection.
Review infrastructure hardening
Identify OpenSSH configuration weaknesses, key exposure risks, and tunneling controls for owned systems.
Translate findings into remediation
Turn SSH test observations into clear report sections, priorities, and owner-ready action items.
Try These Prompts
Create a scoped SSH security checklist for an authorized assessment of [environment]. Include discovery, configuration review, key exposure checks, and reporting.
Given these ssh-audit results: [paste results]. Summarize weak algorithms, authentication risks, and hardening actions.
Plan a permissioned SSH credential exposure test for [scope]. Include rate limits, lockout safeguards, evidence handling, and stop conditions.
Convert these SSH findings into an executive summary, technical findings, severity rationale, and remediation plan: [findings].
Best Practices
- Confirm written authorization, scope, timing, and stop conditions before using any assessment workflow.
- Use isolated lab targets for learning and production-like tests only with approval.
- Record evidence without storing private keys, passwords, or sensitive host data.
Avoid
- Running brute-force or scanning steps against systems outside the approved scope.
- Copying, storing, or reusing private keys found during an assessment.
- Using tunnels or persistence examples on production systems without explicit approval.
Frequently Asked Questions
Is this skill safe for beginners?
Can it run tools for me?
Does it require authorization?
Can it help with defensive hardening?
Does it include credential testing?
Can Claude, Codex, or Claude Code use it?
Developer Details
Author
sickn33License
MIT
Author version
v1.1
Skillstore revision
r1
Version notice
The author-declared version is not valid SemVer.
Repository
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/ssh-penetration-testingRef
3e4b6c31a74a3bd1a291c98cf585d720cb9fbc88
Maintenance freshness
7/18/2026
Usage
10 downloads · 167 views
File structure
📄 SKILL.md