Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides structured technical guidance for executing advanced attack vectors across Active Directory, API authorizations, and security control bypasses. It translates complex exploitation paths into actionable playbooks for professional security assessments.
Penetration testers can use these guides to systematically approach AD ACL abuse, Kerberos attacks, and the circumvention of anti-debugging measures.
WHO IT'S FOR
Penetration testers
executing advanced attack playbooks for AD and APIs
Red team operators
bypassing security controls and anti-debugging measures
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
OpenAPI, Swagger, or other API documentation, if available
In-scope hosts and testing boundaries
Use the api-recon-and-docs skill to perform a first-pass review of my authorized API target. From the supplied base URL, client JavaScript, and any OpenAPI or Swagger documents, produce a compact inventory of reachable entry points, versions, schemas, optional fields, role differences, GraphQL endpoints, mobile paths, and undocumented parameters. Identify the three highest-value areas for follow-up testing without attempting exploitation.
Create a focused two-account authorization test matrix
Uses api-authorization-and-bola
Authorized testing scope
Sanitized request and response captures for Account A
Sanitized request and response captures for Account B
Known object identifiers and role differences
Use the api-authorization-and-bola skill to review the supplied authorized API request captures for Account A and Account B. Create a small replay matrix covering create, read, update, and delete operations, cross-account object identifiers, nested resources, alternate HTTP verbs, and hidden writable fields. Do not execute requests; return the prioritized matrix and the evidence each test should capture.
List of user-controlled fields represented in the export
Use the csv-formula-injection skill to design a minimal, authorized check of the sample export at <sample-export-path>. Start only with benign arithmetic cells such as =1+1 and the documented prefix variants. Explain which user-controlled fields and export sinks to inspect, how to open the file in the named spreadsheet application, and how to record whether each cell remains text, calculates, or raises a warning. Do not use DDE, commands, remote URLs, or external-data functions.
Claude