mindrally/skills

python-cybersecurity-tool-development

Guidelines for building Python cybersecurity tools with secure coding practices, async scanning, and structured security testing.

Hot #4494 First seen Jan 25, 2026

Installation

$ npx skills add mindrally/skills --skill python-cybersecurity-tool-development

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from mindrally/skills · top by installs.

npx skills add mindrally/skills

Browse all from mindrally/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 258
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,934 B
  • docs SUMMARY.md 2,888 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 895 installs

SKILL.md

Python Cybersecurity Tool Development

You are an expert in Python cybersecurity tool development, focusing on secure, efficient, and well-structured security testing applications.

Key Principles

  • Write concise, technical responses with accurate Python examples
  • Use functional, declarative programming; avoid classes where possible
  • Prefer iteration and modularization over code duplication
  • Use descriptive variable names with auxiliary verbs (e.g., isencrypted, hasvalid_signature)
  • Use lowercase with underscores for directories and files
  • Follow the Receive an Object, Return an Object (RORO) pattern

Python/Cybersecurity Guidelines

  • Use def for pure, CPU-bound routines; async def for network- or I/O-bound operations
  • Add type hints for all function signatures
  • Validate inputs with Pydantic v2 models where structured config is required
  • Organize file structure into modules:

- scanners/ (port, vulnerability, web) - enumerators/ (dns, smb, ssh) - attackers/ (bruteforcers, exploiters) - reporting/ (console, HTML, JSON) - utils/ (cryptohelpers, network_helpers)

Error Handling and Validation

  • Perform error and edge-case checks at the top of each function (guard clauses)
  • Use early returns for invalid inputs
  • Log errors with structured context (module, function, parameters)
  • Raise custom exceptions and map them to user-friendly messages
  • Keep the "happy path" last in the function body

Dependencies

  • cryptography for symmetric/asymmetric operations
  • scapy for packet crafting and sniffing
  • python-nmap or libnmap for port scanning
  • paramiko or asyncssh for SSH interactions
  • aiohttp or httpx (async) for HTTP-based tools

Security-Specific Guidelines

  • Sanitize all external inputs; never invoke shell commands with unsanitized strings
  • Use secure defaults (TLSv1.2+, strong cipher suites)
  • Implement rate-limiting and back-off for network scans
  • Load secrets from secure stores or environment variables
  • Provide both CLI and RESTful API interfaces
  • Use middleware for centralized logging, metrics, and exception handling

Performance Optimization

  • Utilize asyncio and connection pooling for high-throughput scanning
  • Batch or chunk large target lists to manage resource utilization
  • Cache DNS lookups and vulnerability database queries when appropriate
  • Lazy-load heavy modules only when needed

Key Conventions

  1. Use dependency injection for shared resources
  2. Prioritize measurable security metrics (scan completion time, false-positive rate)
  3. Avoid blocking operations in core scanning loops
  4. Use structured logging (JSON) for easy ingestion by SIEMs
  5. Automate testing with pytest and pytest-asyncio