Commands

/quicktest

Overview

The /quicktest command starts a rapid penetration test using an AI agent. This mode is optimized for speed and is ideal for quick security assessments, iterative testing during development, or when you need faster results.

Usage

$/quicktest

What is Quick Test?

Quick Test mode performs a streamlined security assessment that:

  • Prioritizes speed over exhaustive coverage
  • Focuses on common vulnerabilities and critical issues
  • Uses efficient testing strategies to minimize time
  • Provides actionable results quickly

Quick Test is perfect for development workflows where you need rapid feedback on security issues without waiting for a comprehensive audit.

How It Works

1

Launch Quick Test

Run /quicktest and provide your target URL or application details

2

AI Reconnaissance

The AI agent performs rapid reconnaissance to identify the attack surface

3

Automated Testing

The agent tests for common vulnerabilities using efficient techniques

4

Real-time Results

Watch findings appear in real-time as the agent discovers vulnerabilities

5

Review Findings

Get immediate access to vulnerability reports with proof-of-concepts

What Gets Tested

Quick Test covers the most critical security areas:

Authentication
  • Weak credentials
  • Session management
  • Authentication bypass
Authorization
  • Access control issues
  • Privilege escalation
  • IDOR vulnerabilities
Injection Attacks
  • SQL injection
  • Command injection
  • XSS vulnerabilities
Common CVEs
  • Known vulnerabilities
  • Outdated dependencies
  • Security misconfigurations

Example Workflow

Here’s a typical Quick Test session:

$# Start Apex
>pensar
>
># Launch quick test
>/quicktest
>
># The agent will prompt for:
># - Target URL or domain
># - Any authentication credentials (optional)
># - Specific areas to focus on (optional)
>
># Watch as the AI agent:
># 1. Discovers endpoints and pages
># 2. Identifies potential vulnerabilities
># 3. Executes test payloads
># 4. Documents findings with POCs

When to Use Quick Test

Run Quick Test frequently during development to catch security issues early.

Benefits:

  • Fast feedback loop
  • Minimal disruption to workflow
  • Early vulnerability detection

Integrate Quick Test into your pipeline for automated security checks.

Use Cases:

  • Pre-deployment checks
  • Pull request validation
  • Continuous security testing

Use Quick Test for first-look security assessments.

Scenarios:

  • Evaluating new acquisitions
  • Third-party application review
  • Quick security baseline

Verify security fixes haven’t introduced new issues.

Applications:

  • Post-patch validation
  • Update verification
  • Change impact assessment

Quick Test vs Thorough Pentest

Understanding when to use each mode:

AspectQuick TestThorough Pentest
DurationMinutes to 1 hourHours to days
CoverageCommon vulnerabilitiesComprehensive
DepthSurface-levelDeep analysis
Best ForDevelopment, CI/CDProduction audits
CostLower token usageHigher token usage

Quick Test is not a substitute for comprehensive security audits. For production applications, use /pentest for thorough coverage.

Configuration Options

When launching Quick Test, you can provide:

Target Information

  • URL/Domain: The application to test
  • Scope: Specific paths or endpoints to focus on

Authentication (Optional)

  • Credentials: Username and password for authenticated testing
  • Tokens: Bearer tokens or API keys
  • Session Data: Cookies or session information

Testing Parameters

  • Focus Areas: Specific vulnerability types to prioritize
  • Exclusions: Endpoints or functionality to skip
  • Rate Limiting: Control request frequency

Interpreting Results

Quick Test provides:

Vulnerability List

Prioritized list of discovered security issues

Severity Ratings

CVSS scores and severity classifications

Proof of Concepts

Working POCs to demonstrate vulnerabilities

Remediation Guidance

Quick fixes and security recommendations

Tips for Better Results

Pro Tips:

  • Provide authentication credentials for deeper testing
  • Use specific scope to focus on critical functionality
  • Run during low-traffic periods to avoid impact
  • Save sessions to resume or re-test later

Saving Your Session

Quick Test sessions can be saved for later review:

  1. During or after testing, the session is automatically saved
  2. Use /sessions to view and resume previous tests
  3. Sessions include all findings, logs, and test data
/pentest

Run a comprehensive penetration test

/sessions

Manage and resume testing sessions

/models

Configure AI model for testing

/config

Adjust testing parameters