scanning-tools
Run Authorized Security Scans
Security teams need consistent workflows for scanning authorized systems without missing common checks. This skill organizes tool choices, commands, reporting steps, and validation guidance for Claude, Codex, and Claude Code.
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 "scanning-tools" from https://skillstore.io/skills/sickn33-scanning-tools.md and its manifest at https://skillstore.io/api/skills/sickn33-scanning-tools/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 "scanning-tools". Create a scan plan for an approved internal subnet and a web application.
Expected outcome:
A phased plan with authorization checks, host discovery, web crawler boundaries, vulnerability validation, evidence handling, and reporting milestones.
Using "scanning-tools". Summarize scanner findings for leadership.
Expected outcome:
An executive summary with risk themes, affected systems, business impact, remediation owners, and follow-up validation steps.
Using "scanning-tools". Troubleshoot a scan that missed expected hosts.
Expected outcome:
A checklist covering scope confirmation, firewall behavior, discovery methods, DNS settings, scanner timing, and connectivity verification.
Security Audit
CriticalThe audit confirms substantial high-risk scanning and exploitation guidance throughout SKILL.md, including Nmap, Masscan, Aircrack-ng, Metasploit, sudo-driven tools, and active web scanners. Several Markdown backtick detections are documentation artifacts, but the skill still instructs users to run intrusive commands and includes critical Internet-scale scanning and exploit validation workflows. No prompt injection text was found.
Confirmed security concerns (59)
Show all 59 confirmed findings
Capability review items (86)
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 (50)
๐ Network access (48)
๐ Filesystem access (3)
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-scanning-tools/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-scanning-tools?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-scanning-tools?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-scanning-tools/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-scanning-tools.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). scanning-tools security audit report (audit version 5) [Author version 1.1]. Skillstore. https://skillstore.io/skills/sickn33-scanning-tools/audits/5BibTeX citation
@techreport{sickn33-sickn33-scanning-tools-2026,
author = {sickn33},
title = {scanning-tools security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-scanning-tools/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: "scanning-tools 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-scanning-tools/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-scanning-tools:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Plan Internal Vulnerability Scans
Create a scoped scan plan that covers discovery, service enumeration, vulnerability checks, and reporting for approved assets.
Prepare Web Application Testing
Select web scanning tools, define crawl and active test boundaries, and organize findings for remediation review.
Collect Compliance Evidence
Use compliance scanners and reporting steps to gather evidence for CIS, PCI-DSS, HIPAA, or internal control reviews.
Try These Prompts
Review my authorized scan scope, time window, and tool list. Identify missing prerequisites and low-impact starting checks.
Create a phased security scan plan for these approved assets: [asset list]. Include discovery, vulnerability checks, validation, and reporting.
Compare these authorized scanner findings. Group duplicates, flag likely false positives, and prioritize issues by business impact.
Design a recurring scanning program for my organization. Include scope controls, safe scan windows, evidence handling, reporting, and escalation rules.
Best Practices
- Confirm written authorization and scope before any scan.
- Start with low-impact discovery, then increase intensity only when approved.
- Record tool versions, time windows, targets, and evidence for every assessment.
Avoid
- Scanning public or third-party targets without written permission.
- Using high-rate or intrusive scans during business hours without coordination.
- Publishing raw scan output that includes secrets, internal addresses, or exploitable details.