red-team-tools-and-methodology
Run Authorized Red-Team Workflows
Security teams need repeatable reconnaissance without losing scope discipline. This skill organizes authorized red-team and bug bounty workflows into practical steps.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "red-team-tools-and-methodology" from https://skillstore.io/skills/sickn33-red-team-tools-and-methodology.md and its manifest at https://skillstore.io/api/skills/sickn33-red-team-tools-and-methodology/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.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 "red-team-tools-and-methodology". Plan first-day reconnaissance for an authorized bug bounty program covering example.com.
Expected outcome:
- A scoped plan that starts with passive discovery and acquisition research.
- A separate active phase for live host checks, content discovery, and controlled scanning.
- A validation phase for duplicate removal, false positive review, and report preparation.
Using "red-team-tools-and-methodology". Prioritize testing for an approved web application with APIs, profiles, and file uploads.
Expected outcome:
- A risk-ranked checklist covering file uploads, API authorization, profile fields, integrations, and error pages.
- Suggested evidence to collect for each finding type.
- Notes to avoid out-of-scope testing and production disruption.
Using "red-team-tools-and-methodology". Turn scanner output into a responsible bug bounty report outline.
Expected outcome:
- A concise finding summary, affected assets, reproduction steps, impact statement, and remediation guidance.
- A reminder to remove false positives and avoid unsupported severity claims.
Security Audit
High RiskThis community skill is a dual-use red-team guide with many runnable reconnaissance, fuzzing, and vulnerability scanning workflows. Several Markdown fence detections are false positives, but command blocks and network examples present real misuse risk without strict authorization controls. No prompt injection attempt was found in SKILL.md.
Confirmed security concerns (4)
Capability review items (19)
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 (29)
🌐 Network access (6)
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-red-team-tools-and-methodology/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-red-team-tools-and-methodology?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-red-team-tools-and-methodology?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-red-team-tools-and-methodology/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-red-team-tools-and-methodology.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). red-team-tools-and-methodology security audit report (audit version 5) [Author version 1.1]. Skillstore. https://skillstore.io/skills/sickn33-red-team-tools-and-methodology/audits/5BibTeX citation
@techreport{sickn33-sickn33-red-team-tools-and-methodology-2026,
author = {sickn33},
title = {red-team-tools-and-methodology security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-red-team-tools-and-methodology/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: "red-team-tools-and-methodology security audit report (audit version 5)"
version: "1.1"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-red-team-tools-and-methodology/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-red-team-tools-and-methodology:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Plan Bug Bounty Reconnaissance
Build a scoped workflow for passive discovery, live host checks, content discovery, and finding triage.
Structure Internal Assessments
Create a repeatable checklist for authorized application mapping, API review, vulnerability scanning, and evidence collection.
Teach Web Testing Methodology
Use the tool list and workflow sections to teach responsible reconnaissance and validation practices.
Try These Prompts
I have written authorization to test example.com. Build a scoped reconnaissance plan using this skill. Include inputs, tools, outputs, and rate limits.
Create a subdomain and live-host enumeration checklist for an approved bug bounty target. Put passive steps before active steps.
Review these allowed assets and technologies. Prioritize content discovery, API checks, and XSS testing by risk and effort.
Design an authorized recon pipeline for multiple domains. Include storage layout, tool order, validation steps, rate limits, and report-ready artifacts.
Best Practices
- Confirm written authorization, target scope, rate limits, and prohibited techniques before active testing.
- Run passive discovery before active probing, then document each tool, input, output, and timestamp.
- Manually verify automated findings before disclosure, and remove duplicates or false positives from reports.
Avoid
- Testing domains, IPs, or subsidiaries that are not explicitly in scope.
- Running fuzzing or vulnerability scans without rate limits or production safeguards.
- Submitting scanner output without manual validation, reproduction steps, and impact analysis.
Frequently Asked Questions
Is this skill only for authorized testing?
Does the skill install tools automatically?
Can it run active scans?
Does it validate vulnerabilities?
What targets should users provide?
Is it suitable for training?
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/web-app/public/skills/red-team-toolsRef
9f814fc6a43fd99946f2da5e0df231c65a38bc76
Maintenance freshness
7/18/2026
Usage
6 downloads · 133 views
File structure
📄 SKILL.md