Assess web applications for path traversal, a flaw that exposes files outside intended folders. Follow structured checks to identify vulnerable inputs, document demonstrated access, assess data exposure, and prepare remediation guidance.
- Checking file download features for path traversal
- Investigating local file inclusion risks
- Testing file access behavior on Linux and Windows
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Guides authorized security assessments with Metasploit, from scanning and vulnerability testing to payload generation, code used during a test, and post-exploitation investigation. It also covers session management and recording evidence of findings.
- Checking vulnerabilities in an authorized test environment
- Finding modules for a specific CVE
- Reviewing system information after a test compromise
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Runs HTTP load tests with gradually increasing concurrent connections. It measures response-time percentiles, throughput, and errors, identifies where performance starts to deteriorate, and recommends a concurrency level based on the results.
- Benchmarking an API under increasing load
- Finding concurrency levels where p99 latency rises
- Checking throughput saturation and error growth
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Test whether changing record IDs or filenames exposes another user's data in a web application. This skill guides access control checks, evidence collection, impact assessment, and fixes for IDOR, a flaw in resource authorization.
- Check access controls between test accounts
- Review permissions on receipt and document downloads
- Document affected endpoints and supporting evidence
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Learn how to conduct an authorized penetration test, a security assessment that checks exploitable weaknesses. Follow guidance from initial research and scanning through validation, evidence collection, and reporting with remediation recommendations.
- Learning the full penetration testing lifecycle
- Planning research and scanning for an authorized assessment
- Organizing vulnerability evidence
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Explains how to assess paths from limited user access to administrator privileges on Linux and Windows. Covers local permission weaknesses and Active Directory, a Windows domain management system, with tool selection and documentation guidance for authorized testing.
- Reviewing Linux privilege settings
- Assessing Windows services and privileges
- Examining Active Directory escalation paths
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Test web applications for HTML injection, where user input becomes page markup. Identify affected inputs, verify stored or reflected behavior, assess visual manipulation and phishing risks, and document findings with remediation guidance.
- Checking forms and search fields for HTML injection
- Distinguishing stored and reflected injection
- Assessing page manipulation and phishing risks
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Scan projects for known dependency vulnerabilities, exposed credentials, and risky code patterns such as SQL injection. Produces text or JSON reports with file locations and severity levels, with options to run individual checks.
- Checking dependency vulnerabilities before release
- Finding hardcoded API keys and passwords
- Reviewing code for common security weaknesses
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Set up HTTP, HTTPS, SNMP for device information, and SMB for file sharing in a penetration testing lab. Follow configuration and testing steps to inspect exposed information, check access permissions, and review service logs.
- Setting up a web server in a testing lab
- Checking HTTPS connections with a self-signed certificate
- Practicing SNMP information discovery
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Create Playwright tests for user workflows, APIs, and visual changes. Use TypeScript or JavaScript examples to choose reliable page elements, manage login state, diagnose intermittent failures, and configure automated test runs in CI.
- Testing login, forms, and other user workflows
- Checking APIs, visual changes, and accessibility
- Diagnosing tests that fail intermittently
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Assess AWS security through penetration testing, a process for checking exploitable weaknesses. Examine IAM permissions, storage, compute resources, and credential exposure to identify privilege escalation paths and document security audit findings.
- Review IAM permissions for privilege escalation paths
- Assess S3 bucket access and exposed files
- Check credential exposure through EC2 metadata
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Assess Linux systems for weaknesses that let a regular user gain administrator access. Guides inspection of permissions, scheduled tasks, and vulnerable components, with findings, evidence, and remediation recommendations documented for review.
- Auditing Linux permissions and configuration
- Checking sudo and SUID privilege escalation paths
- Reviewing scheduled tasks and shared directories
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Assess Azure, AWS, and GCP security through resource inventories, authentication checks, permission reviews, and misconfiguration testing. Supports authorized assessments that document exposed credentials, rate risks, and recommend improvements for each cloud platform.
- Inventorying cloud resources and permissions
- Checking for exposed credentials and secrets
- Testing the impact of cloud misconfigurations
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Plan and coordinate penetration tests with checklists covering objectives, scope, environment preparation, tester selection, monitoring, and follow-up. Helps teams define deliverables, prioritize vulnerabilities, arrange fixes and verification, and clean up test accounts and artifacts.
- Defining penetration test objectives and scope
- Preparing test environments and monitoring
- Selecting testers and agreeing on report requirements
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Test REST, SOAP, and GraphQL APIs for authentication flaws, improper access to other users’ records, and unsafe input handling. Guides endpoint discovery and request variations to identify vulnerabilities and document evidence of unauthorized access.
- Discovering API endpoints for security testing
- Checking access to other users’ records
- Assessing GraphQL schemas and query handling
zebbern/claude-code-guide☆ 4.7KUpdated Oct 24, 2026
Check code and agent outputs, track reliability scores, and roll back changes that fail a chosen threshold. Includes quality reports, live monitoring, and integration with automated build and deployment workflows.
- Checking code produced by AI agents
- Rolling back changes that fail verification
- Tracking quality trends over time
ruvnet/RuVector☆ 4.6KUpdated Oct 25, 2026
Review and strengthen security in claude-flow v3 by addressing dependency risks, password hashing, credential generation, input validation, file paths, and command execution. It also guides threat modeling and tests for security-critical code.
- Reviewing security boundaries and potential threats
- Updating dependencies and checking audit results
- Revising password hashing and credential generation
ruvnet/RuVector☆ 4.6KUpdated Oct 25, 2026
Look across feedback, operational data, errors, and delivery failures over a defined period to find recurring problems. Trace patterns to shared causes, examine earlier fixes, and recommend systemic changes, implementing and verifying them only when configured policies allow.
- Review recurring problems across feedback and operational records
- Investigate symptoms that returned after an earlier fix
- Find shared causes across related features and callers
BuilderIO/skills☆ 4.6KUpdated Oct 22, 2026
Verify BB workflows in an isolated development app using browser interactions and the matching source CLI. Select relevant checks, collect screenshots and persisted-state evidence, and report passes, failures, untested cases, and blockers separately.
- Check affected workflows after a BB feature change
- Run a smoke test of BB's main interactions
- Audit verification coverage against source changes
get-bb/bb☆ 4.6KUpdated Oct 25, 2026
Collect user-provided API keys and other credentials through a form and save them to a specified dotenv configuration file. Request multiple variables together without exposing their values in chat, command arguments, or output visible to the agent.
- Configure API keys in .env.local
- Request several credentials in one form
- Update credentials without sharing values in chat
get-bb/bb☆ 4.6KUpdated Oct 25, 2026
Create a repository-specific verification skill and a comprehensive feature map for an app. It documents launch, UI, CLI, and API checks, then runs the instructions to capture evidence and distinguish verified features from untested or blocked ones.
- Create verification instructions for agents new to a repository
- Map app features and their observable success conditions
- Prove a real user journey and preserve evidence
get-bb/bb☆ 4.6KUpdated Oct 25, 2026
Audit an existing app verification skill against source code and the running application. Update outdated instructions, feature maps, and test helpers using evidence, while reporting product bugs and blocked checks separately.
- Refresh verification steps after app changes
- Find missing features in a verification map
- Repair helpers that cannot run valid checks
get-bb/bb☆ 4.6KUpdated Oct 25, 2026
Review new and existing tests for meaningful behavior coverage, duplication, and dependence on implementation details. Gather evidence before cleanup, preserve tests that protect independent contracts, and verify that removed tests leave their regression checks covered elsewhere.
- Review the value of new or changed tests
- Find duplicate tests and implementation-dependent assertions
- Audit production code kept only for tests
get-bb/bb☆ 4.6KUpdated Oct 25, 2026
Run Unity tests in EditMode or PlayMode, selecting specific assemblies, namespaces, classes or methods. Review individual outcomes and durations, filter results, and include failure messages, logs or stack traces to investigate problems.
- Rerun a specific test class after changes
- Run tests in EditMode or PlayMode
- Review only failed test results
IvanMurzak/Unity-MCP☆ 4.5KUpdated Oct 24, 2026