authentication-session-validation
/authentication-session-validation
Build repeatable AgentWorks browser validation for authentication and session behavior. Use for login, logout, MFA, recovery, expiry, refresh, and invalid-session coverage after browser setup.
- Author
- manishiitg ↗
- Repository
- agentworks ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Build repeatable AgentWorks browser validation for authentication and session behavior. Use for login, logout, MFA, recovery, expiry, refresh, and invalid-session coverage after browser setup.
Original author description
Build repeatable AgentWorks browser validation for authentication and session behavior. Use for login, logout, MFA, recovery, expiry, refresh, and invalid-session coverage after browser setup.
How it works
- Outcome
- When to use
- Discovery and user direction
- Required inputs
- Plan and AgentWorks tools
- Knowledge and persistence
- Validation and reporting
- Guardrails
- Read details when needed
- Completion contract
SKILL.md preview
--- name: authentication-session-validation description: Build repeatable AgentWorks browser validation for authentication and session behavior. Use for login, logout, MFA, recovery, expiry, refresh, and invalid-session coverage after browser setup. --- # Authentication and Session Validation ## Outcome Create repeatable, role-aware tests for the application's approved authentication and session lifecycle with durable results and attempt-scoped evidence. ## When to use Use after Basic Browser Setup when authentication behavior needs coverage beyond establishing one working test session. Include only flows enabled and authorized for the customer environment. ## Discovery and user direction Inspect the current workflow, goals, metrics, configuration, capabilities, stores, reports, and triggers before proposing changes. Summarize reusable design and gaps, then ask focused questions for unresolved customer choices such as scope, success, approvals, thresholds, ownership, and budgets. Record the answers as customer direction. Installation alone does not approve workflow changes or execution. Default to one small-team workflow; split only for incompatible access or lifecycle boundaries. ## Required inputs Resolve authentication methods, actor roles, approved expectations, account ownership, MFA/recovery channels, session lifetime rules, lockout limits, allowed state changes, evidence retention, and cleanup/reset procedures. ## Plan and AgentWorks tools Use scripted steps for repeatable Playwright scenarios and deterministic persistence. Use a message sequence for evidence-based investigation. Add branches only for real outcome paths or configured review. Reuse selected secrets and never pass secret values through plan context. ## Knowledge and persistence Keep secret references in workflow configuration. Store verified routes, session behavior, role requirements, and non-secret auth quirks in application KB notes. Store runs, cases, attempts, and artifact metadata in the DB and video plus redacted console/network evidence in durable assets. ## Validation and reporting Require a terminal result for every expected auth scenario and actor. Verify fresh-context behavior, post-action state, required cleanup, source/build identity, and evidence status. The dashboard shows the scenario/actor matrix, environment and build, failure class, evidence status, and history without exposing credentials or tokens. ## Guardrails Do not trigger unapproved lockouts, recovery messages, enrollment changes, account deletion, or production authentication experiments. Never persist passwords, cookies, tokens, MFA seeds/codes, storage state, or unrestricted network bodies. ## Read details when needed - [Workflow design and outcomes](../../references/workflow-design-and-outcomes.md): goals, metrics, and current-versus-separate workflow decisions. - [AgentWorks plan and tools](../references/agentworks-plan-and-tools.md): step and platform-tool choices. - [Evidence capture](../references/evidence-capture.md): durable, redacted attempt evidence. - [Authentication guide](references/authentication-workflow.md): scope, flow, storage, and acceptance cases. - [Example scenarios](examples/authentication-scenarios.json): fictional coverage shape. - [Catalog metadata](playbook.json): presentation and optional recommendations. ## Completion contract Return installed playbook and scenario revisions, customer overrides, actor/scenario coverage, actual trial results, KB/test/evidence/report locations, capability resolution, and unresolved or unsafe-to-test behavior.
Files in this package (4)
- SKILL.md 4 KB
- playbook.json 4 KB
- examples/authentication-scenarios.json 1 KB
- references/authentication-workflow.md 3 KB
Versions
The database has no other skills named authentication-session-validation.
Database snapshot: 13.11.2026 · package version 781777098323 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90security-authentication-and-sessions
Assess and remediate authentication, sessions, identity tokens, mfa, federated sign-in and logout in frontend and associated web services. Use for login, session renewal or expiry, cookies, MFA, OAuth, OIDC, JWT, account recovery. - 100browser-performance-validation
Build repeatable AgentWorks browser performance validation with customer-defined budgets and comparable samples. Use for page, journey, Web Vital, resource, or timing regressions. - 100auth-flow-validation
Authentication flow validation between frontend and backend. Covers JWT, OAuth2, token refresh, and session management sync. USE WHEN: user asks about "auth integration", "JWT validation", "token refresh", "401 handling", "authentication flow", "login integration" DO NOT USE… - 100authentication-flow
Implements authentication using Rails 8 built-in generator. Use when setting up user authentication, login/logout, session management, password reset flows, or securing controllers. WHEN NOT: Authorization and permissions (use Pundit policies), API token authentication,… - 90authentication-failures
Detects weak password storage, flawed JWT validation, sessions surviving logout, and missing MFA in authentication code. Use when writing login flows, session management, password storage, JWT handling, MFA implementation, credential validation, or any code that authenticates… - 95auth0-flask
Use when adding login, logout, and user profile to a Flask web application using session-based authentication - integrates auth0-server-python for server-rendered apps with login/callback/profile/logout flows.