mirror of
https://github.com/davila7/claude-code-templates.git
synced 2026-09-19 01:30:23 +08:00
Dani
054c0e56e9
Removed the deprecated 'model: sonnet' field from command frontmatter to fix compatibility issues with Claude Code. Commands will now inherit the model from the active conversation instead of using a hardcoded deprecated model identifier. Changes: - Removed 'model: sonnet' from 142 command files across all categories - Commands now use default model inheritance behavior - Preserved 'model: claude-sonnet-4-5-20250929' in gemini-review.md (valid model) - 67 commands without model field remain unchanged This resolves the "model: sonnet not found" error reported in GitHub issues and aligns with Claude Code's recommended practice of letting commands inherit the conversation model. Affected categories: - Database/Supabase commands (8 files) - Documentation commands (8 files) - Deployment commands (11 files) - Setup commands (14 files) - Performance commands (8 files) - Team commands (14 files) - Security commands (6 files) - NextJS/Vercel commands (10 files) - Sync commands (14 files) - And more across other categories 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
1.8 KiB
1.8 KiB
allowed-tools: Read, Bash, Grep, Glob
argument-hint: [target] | --web-app | --api | --auth | --full-scan
description: Perform penetration testing and vulnerability assessment on application
Penetration Test
Perform penetration testing and vulnerability assessment: $ARGUMENTS
Application Context
- Running services: !
netstat -tlnp 2>/dev/null | grep LISTEN | head -10 || lsof -i -P | grep LISTEN | head -10 - Web framework: @package.json or @requirements.txt (detect framework and version)
- API endpoints: !
grep -r "route\|endpoint\|@app\\.route\|@RequestMapping" src/ 2>/dev/null | wc -l - Authentication: !
grep -r "auth\|login\|jwt\|session" src/ 2>/dev/null | wc -l
Task
Conduct systematic penetration testing following ethical hacking methodologies:
Test Target: Use $ARGUMENTS to focus on web application, API, authentication, or comprehensive testing
Testing Phases:
- Reconnaissance - Service discovery, technology fingerprinting, attack surface mapping
- Vulnerability Assessment - OWASP Top 10, injection flaws, broken authentication
- Exploitation Testing - XSS, CSRF, SQL injection, privilege escalation attempts
- Authentication Testing - Brute force, session management, authorization bypasses
- API Security Testing - Input validation, rate limiting, authentication bypass
- Infrastructure Testing - Network security, container security, configuration issues
Testing Methodology:
- Follow OWASP Testing Guide and NIST guidelines
- Use both automated tools and manual testing techniques
- Document all findings with proof-of-concept examples
- Provide remediation recommendations for each vulnerability
- Maintain ethical boundaries and avoid data damage
Output: Comprehensive penetration test report with executive summary, detailed findings, risk ratings, and remediation roadmap.