Search Results for "narlyseorg" | AgentCC

Secure Code Review

Use when reviewing source code for security vulnerabilities, performing static analysis of a codebase, or auditing code for injection flaws, authentication issues, cryptographic weaknesses, insecure deserialization, SSRF, path traversal, memory-safety bugs, hardcoded secrets, or misconfigurations. Use when the user asks to find security bugs in code, assess code quality from a security perspective, review pull requests for security implications, perform dependency audits, run secrets scans, or review application configuration in source.

finishing-an-engagement

Use when active testing is complete, all findings are verified, and you need to finalize the engagement — guides completion by presenting structured options for report delivery, evidence archival, artifact cleanup, and client handoff

infra-pentesting

Use when testing network infrastructure, servers, or internal/external networks. Triggers: host discovery, port scanning, service enumeration, vulnerability assessment, exploitation of network services, Active Directory attacks, password cracking, lateral movement, pivoting, privilege escalation, cloud infrastructure testing, network-level attacks like MITM or ARP spoofing. Covers TCP/UDP services including SSH, FTP, SMB, RDP, SNMP, DNS, LDAP, Kerberos, WinRM. Applies to both Linux and Windows targets in on-prem and cloud environments.

Android Pentesting

Use when testing Android applications for security vulnerabilities. Triggers: APK analysis, mobile app assessment, Android static analysis, dynamic analysis, runtime manipulation with Frida, traffic interception with mitmproxy, SSL pinning bypass, root detection bypass, insecure data storage testing, exported component abuse, deeplink fuzzing, content provider exploitation, reverse engineering Android apps, OWASP Mobile Top 10 assessment, certificate pinning testing, biometric bypass, intent injection.

webapp-pentesting

Use when testing web applications for security vulnerabilities, performing webapp penetration tests, assessing OWASP Top 10 risks, testing for XSS/SQLi/CSRF/SSRF/IDOR/auth bypass, fuzzing web endpoints, scanning web servers, intercepting HTTP traffic, testing file uploads, evaluating session management, or when the target is a browser-accessible web application requiring comprehensive security assessment.

exploit-development

Use when needing to exploit a confirmed vulnerability, generate payloads, craft reverse shells, use Metasploit modules, write custom exploit scripts, perform post-exploitation, escalate privileges, pivot through networks, bypass security controls, or when the user asks to exploit, pwn, pop a shell, gain access, or weaponize a finding.

using-git-worktrees

Use when starting security work that needs isolation from current workspace, before executing engagement plans, or when testing exploits that could affect the working tree — creates isolated git worktrees with smart directory selection and safety verification

writing-security-skills

Use when creating new superhackers security skills, editing existing security skills, reviewing skill quality before deployment, or when a gap is discovered during a security engagement and needs to be captured as a reusable skill.

using-superhackers

Use when starting any security task, pentest, vulnerability assessment, code review, recon, exploit development, or security assessment. Use FIRST before loading any other superhackers skill. Use when unsure which security skill to load. Use when planning a multi-phase security engagement.

recon-and-enumeration

Use when starting a new engagement, scoping a target, gathering intelligence before exploitation, discovering attack surface, enumerating services and technologies, performing subdomain discovery, identifying entry points, or when the user asks to scan, enumerate, fingerprint, or map a target network or application.

API Pentesting

Use when testing APIs for security vulnerabilities, assessing REST/GraphQL/gRPC/WebSocket/SOAP endpoints, testing API authentication and authorization (OAuth2, JWT, API keys), discovering undocumented API endpoints, testing for BOLA/IDOR in API resources, performing API fuzzing, analyzing API traffic, testing rate limiting, or when the target exposes programmatic interfaces requiring security assessment per OWASP API Security Top 10.

Vulnerability Verification

Use when a scanner or manual testing has identified a potential vulnerability that needs confirmation, when eliminating false positives from automated scan results, when determining real-world exploitability and impact of a finding, when collecting evidence for a security report, when chaining multiple low-severity issues into a higher-impact attack, or when verifying that a patch or remediation actually fixes a vulnerability.

dispatching-parallel-agents

Use when facing 2 or more independent security tasks that can be worked on without shared state or sequential dependencies — e.g., parallel scans across targets, simultaneous testing of unrelated attack surfaces, or concurrent investigation of independent findings.

writing-security-reports

Use when documenting security findings, writing pentest reports, creating vulnerability advisories, drafting executive summaries for security assessments, formatting evidence for security deliverables, scoring vulnerabilities with CVSS, writing remediation guidance, or producing any security assessment documentation deliverable.

security-assessment

Use when planning, scoping, or executing a comprehensive security assessment, penetration test, red team engagement, or security audit. Use when the user needs to coordinate multiple security testing activities, define assessment scope and rules of engagement, perform threat modeling, rate risk using CVSS, map findings to compliance frameworks (OWASP Top 10, PCI DSS, SOC 2, ISO 27001), manage assessment lifecycle from planning through reporting, or orchestrate multiple security skills together. Use as the master coordinator when no single specialized skill covers the full task.