senior-security

Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security ass...

Security Scan

The skill's claims (comprehensive, production-grade pentest and audit tooling across many stacks) do not match the actual bundle (small placeholder Python scripts and docs); it looks like an incomplete or misrepresented package rather than a ready, coherent tool.

Purpose & Capability

The name and description promise comprehensive, production-grade security tooling across many languages, clouds, and CI/CD stacks, but the package contains only three small Python scaffold scripts that perform no real analysis and three reference markdown files. Tech stack and dev workflow entries (npm, Docker, .env.example, requirements.txt) are not present in the repository, which is disproportionate to the stated purpose.

Instruction Scope

SKILL.md instructs running the included scripts against an arbitrary <target-path>. The scripts validate that the path exists and then run stubbed analysis (they do not read or exfiltrate data in their current form), but invoking them will cause the skill to access filesystem paths provided by the caller. The documentation also directs steps (npm install, cp .env.example) that reference files not present in the bundle.

Install Mechanism

No install spec is provided (instruction-only skill with code files). That minimizes installation risk because nothing is downloaded or extracted during install.

Credentials

Declared requirements list no env vars or credentials, but SKILL.md suggests creating/copying an .env file and running npm/pip installs — a mismatch. The skill does not justify the broad tech stack and CI/CD/cloud items it lists, and there are no declared credentials even though real pentest/audit tooling would often require service API keys or privileged access.

Persistence & Privilege

always is false and there is no install-time modification of agent/system configuration. The skill does not request persistent or elevated platform privileges.

What to consider before installing

This package appears to be a lightweight placeholder rather than the comprehensive, production-ready security toolkit it advertises. Before installing or using it: 1) Expect the Python scripts to be stubs — review the scripts line-by-line and run them in a sandbox with non-sensitive test data. 2) Ask the publisher for missing files the README references (requirements.txt, package.json, .env.example, CI configs) and for evidence of maintenance/real functionality. 3) Be cautious when passing real project paths or credentials to the tools — the scripts accept arbitrary target paths and could be extended later to read or modify files. 4) If you need production-grade pentest/audit tooling, prefer well-known maintained tools and verify provenance and release artifacts. If you want, I can list exact lines to inspect or produce a checklist of tests to validate functionality and safety.

Complete toolkit for senior security with modern tools and best practices.

Quick Start

Main Capabilities

This skill provides three core capabilities through automated scripts:

# Script 1: Threat Modeler
python scripts/threat_modeler.py [options]

# Script 2: Security Auditor
python scripts/security_auditor.py [options]

# Script 3: Pentest Automator
python scripts/pentest_automator.py [options]

Core Capabilities

1. Threat Modeler

Automated tool for threat modeler tasks.

Features:

• Automated scaffolding
• Best practices built-in
• Configurable templates
• Quality checks

Usage:

python scripts/threat_modeler.py <project-path> [options]

2. Security Auditor

Comprehensive analysis and optimization tool.

Features:

• Deep analysis
• Performance metrics
• Recommendations
• Automated fixes

Usage:

python scripts/security_auditor.py <target-path> [--verbose]

3. Pentest Automator

Advanced tooling for specialized tasks.

Features:

• Expert-level automation
• Custom configurations
• Integration ready
• Production-grade output

Usage:

python scripts/pentest_automator.py [arguments] [options]

Reference Documentation

Security Architecture Patterns

Comprehensive guide available in references/security_architecture_patterns.md:

• Detailed patterns and practices
• Code examples
• Best practices
• Anti-patterns to avoid
• Real-world scenarios

Penetration Testing Guide

Complete workflow documentation in references/penetration_testing_guide.md:

• Step-by-step processes
• Optimization strategies
• Tool integrations
• Performance tuning
• Troubleshooting guide

Cryptography Implementation

Technical reference guide in references/cryptography_implementation.md:

• Technology stack details
• Configuration examples
• Integration patterns
• Security considerations
• Scalability guidelines

Tech Stack

Languages: TypeScript, JavaScript, Python, Go, Swift, Kotlin Frontend: React, Next.js, React Native, Flutter Backend: Node.js, Express, GraphQL, REST APIs Database: PostgreSQL, Prisma, NeonDB, Supabase DevOps: Docker, Kubernetes, Terraform, GitHub Actions, CircleCI Cloud: AWS, GCP, Azure

Development Workflow

1. Setup and Configuration

# Install dependencies
npm install
# or
pip install -r requirements.txt

# Configure environment
cp .env.example .env

2. Run Quality Checks

# Use the analyzer script
python scripts/security_auditor.py .

# Review recommendations
# Apply fixes

3. Implement Best Practices

Follow the patterns and practices documented in:

• references/security_architecture_patterns.md
• references/penetration_testing_guide.md
• references/cryptography_implementation.md

Best Practices Summary

Code Quality

• Follow established patterns
• Write comprehensive tests
• Document decisions
• Review regularly

Performance

• Measure before optimizing
• Use appropriate caching
• Optimize critical paths
• Monitor in production

Security

• Validate all inputs
• Use parameterized queries
• Implement proper authentication
• Keep dependencies updated

Maintainability

• Write clear code
• Use consistent naming
• Add helpful comments
• Keep it simple

Common Commands

# Development
npm run dev
npm run build
npm run test
npm run lint

# Analysis
python scripts/security_auditor.py .
python scripts/pentest_automator.py --analyze

# Deployment
docker build -t app:latest .
docker-compose up -d
kubectl apply -f k8s/

Troubleshooting

Common Issues

Check the comprehensive troubleshooting section in references/cryptography_implementation.md.

Getting Help

• Review reference documentation
• Check script output messages
• Consult tech stack documentation
• Review error logs

Resources

• Pattern Reference: references/security_architecture_patterns.md
• Workflow Guide: references/penetration_testing_guide.md
• Technical Guide: references/cryptography_implementation.md
• Tool Scripts: scripts/ directory