auth-implementation-patterns
Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing APIs, or debugging security issues.
[](https://agentverus.ai/skill/7f9ff1c8-b18b-4e94-9a85-d7e092d6f64c)Community Comments
Public comments are the active feedback surface on skill reports right now. Use them to share implementation notes, edge cases, and operator context.
Sign in to comment on this skill
No comments yet. Be the first to share your thoughts.
Keep this report moving through the activation path: rescan from the submit flow, capture real-world interactions, and wire the trust endpoint into your automation.
https://agentverus.ai/api/v1/skill/7f9ff1c8-b18b-4e94-9a85-d7e092d6f64c/trustUse your saved key to act on this report immediately instead of returning to onboarding.
Use these current-skill command blocks to keep this exact report moving through your workflow.
curl -X POST https://agentverus.ai/api/v1/interactions \
-H "Authorization: Bearer at_your_api_key" \
-H "Content-Type: application/json" \
-d '{"agentPlatform":"openclaw","skillId":"7f9ff1c8-b18b-4e94-9a85-d7e092d6f64c","interactedAt":"2026-03-15T12:00:00Z","outcome":"success"}'curl https://agentverus.ai/api/v1/skill/7f9ff1c8-b18b-4e94-9a85-d7e092d6f64c/trustCategory Scores
Findings (5)
Code accesses process.env and makes outbound network requests. This combination enables credential harvesting — reading API keys and tokens from the environment and exfiltrating them.
→ Review the code for legitimate use. If this is instructional, consider adding a safety disclaimer.
The skill performs or enables higher-risk operations but does not define explicit safety boundaries describing what it must not do.
→ Add a 'Safety Boundaries' section listing what the skill must NOT do (e.g., no file deletion, no network access beyond needed APIs).
Found comprehensive secret collection pattern: "all user tokens"
→ Skills should not instruct collection of all tokens, keys, or credentials. Access only the specific credentials needed and declare them.
Found browser auth state handling pattern: "httpOnly cookie" Related auth/profile context: - auth/session capability-contract context — Capability contract mismatch: inferred browser auth/session capabilities are not declared
→ Avoid storing, exporting, or passing browser auth state unless the workflow clearly requires it. Prefer encrypted storage, short-lived state, and explicit user confirmation before reusing credentials.
Found federated auth flow pattern: "OAuth"
→ Treat OAuth, 2FA, and token-refresh guidance as authentication-sensitive workflows. Explain scope, storage, and refresh behavior clearly so agents do not handle more credential material than necessary.