252 skills (repositories by ajtazer) · sorted by popularity
Detect code injection vulnerabilities in packages that dynamically generate or evaluate code via new Function(), eval(), vm.run*, or template literal interpolation.
The English summary is being prepared. Showing the original description.
Detect OS command injection via shell execution sinks where user-controlled input reaches system commands without proper sanitization.
The English summary is being prepared. Showing the original description.
You are helping a penetration tester extract credentials from Active
The English summary is being prepared. Showing the original description.
You are helping a penetration tester exploit Kerberos delegation misconfigurations
The English summary is being prepared. Showing the original description.
You are helping a penetration tester perform Kerberoasting (extracting TGS
The English summary is being prepared. Showing the original description.
NTLM info disclosure is a Medium-severity finding when chained to context — the leak itself is intentional protocol behavior (RFC-compliant NTLMSSP challenge), but on internet-exposed enterprise infrastructure it provides exact reconnaissance for the next stage of an attack. Highest-value targets:
The English summary is being prepared. Showing the original description.
You are orchestrating a penetration test using Claude Code agent teams. You
The English summary is being prepared. Showing the original description.
You are helping a penetration tester enumerate and exploit Active Directory
The English summary is being prepared. Showing the original description.
You are helping a penetration tester use credential material (NTLM hashes,
The English summary is being prepared. Showing the original description.
You are helping a penetration tester exploit ADCS through template/CA access
The English summary is being prepared. Showing the original description.
You are helping a penetration tester perform password spraying against
The English summary is being prepared. Showing the original description.
Cross-cutting methodology for the CVE-hunting pipeline (ported from find-cve-agent): when a bug is design-vs-real, false-positive avoidance, version checking before reporting, responsible disclosure norms, acceptance-rate expectations per vuln class, vulnerability chaining playbook, known false-positive patterns, maintainer-response patterns, secure-pattern reference (what NOT to flag), and a self-criticism checklist to run before claiming a finding. Use this alongside the cve-hunter/cve-exploiter/cve-validator agents and the /cve-hunt pipeline — load it whenever judging if a finding is real, worth reporting, or already fixed.
The English summary is being prepared. Showing the original description.