auth-agent

Detect authentication and authorization flaws in web and API targets.

241|28|Updated May 20, 2026
One-click install
npx skills add https://github.com/ok-helloworld/vibe-pentest --skill auth-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth-agent
Source: https://github.com/ok-helloworld/vibe-pentest/tree/main/agents/auth-agent
Command: npx skills add https://github.com/ok-helloworld/vibe-pentest --skill auth-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Eliminates blind spots in web security testing by systematically validating authentication and authorization boundaries across login, session, token, and user/resource access paths.

Core Features & Use Cases

  • 认证绕过与会话/令牌缺陷检测:覆盖认证绕过、会话管理缺陷、JWT/OAuth/OIDC/SAML 相关风险,并要求用可回放的 HTTP 证据支撑结论。
  • IDOR/越权的对照验证:围绕对象级授权缺陷执行 A/B 账号对比与状态边界复核,确保权限判定可被验证复现。
  • 暴力破解与防护评估(条件执行):依据 strategy.json 的 brute_force 配置决定是否进行受控测试,并同时检查限流/锁定等防护行为。

Quick Start

Ask the agent to perform full authentication and authorization testing for your target URL using your provided authorization scope, test accounts, and any available logged-in session artifacts so it can produce reproducible HTTP evidence.

Frequently Asked Questions about auth-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test for IDOR and authorization bypass vulnerabilities in web APIs?

To test for IDOR and authorization bypass, you systematically enumerate object authorization paths using A/B account comparisons. This validates trust-boundary failures by capturing reproducible HTTP evidence to confirm permission gaps.

What is the best way to detect JWT and OAuth protocol misconfigurations?

Detecting JWT and OAuth misconfigurations requires exercising token validation paths with deterministic HTTP testing. This identifies protocol misconfigurations, insecure randomness, and session management defects backed by strict evidence capture.

How does brute force testing evaluate rate limiting and account lockout protections?

Brute force testing evaluates rate limiting by executing controlled attacks driven by configuration rules. It simultaneously checks lockout behaviors and throttling mechanisms to determine if authentication endpoints resist automated credential stuffing.

Can I perform SSO and SAML authentication testing without prior security expertise?

Performing SSO and SAML testing requires providing target URLs, authorization scopes, and test accounts. Systematic validation of trust boundaries across login and session paths requires deterministic HTTP testing to produce reproducible evidence.

Why does user enumeration occur during login flow testing and how is it detected?

User enumeration occurs during login flow testing when authentication responses reveal whether an account exists. It is detected by exercising login paths and analyzing HTTP responses to identify trust-boundary failures and protocol misconfigurations.

What HTTP evidence is needed to reproduce an authentication bypass vulnerability?

Reproducing an authentication bypass requires deterministic HTTP testing artifacts capturing exact request and response pairs. This strict evidence capture ensures the trust-boundary failure can be replayed and verified during authorization validation.