rcode-auth-audit

Audit authentication and tenant-isolation failures in multi-organization systems.

2|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/hanzlahabib/rcode --skill rcode-auth-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rcode-auth-audit
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/core/rcode-auth-audit
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-auth-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps catch subtle authentication and authorization failures before they become production incidents, such as stale sessions, broken sync, and tenant data leakage.

Core Features & Use Cases

  • Auth surface review: Checks login, refresh, logout, role change, password reset, and callback flows for security gaps.
  • Identity sync validation: Verifies Keycloak and Active Directory synchronization behavior, token revocation, and session invalidation rules.
  • Tenant isolation checks: Reviews Postgres access patterns, row-level security, and tenant_id enforcement to prevent cross-tenant reads or writes.
  • Use case: Use this Skill when an app shows ghost sessions, users disappear after sync, or multi-tenant data appears accessible across organizations.

Quick Start

Ask the assistant to audit the authentication flows in your project and produce a line-by-line checklist of sync, JWT, session, and tenant-isolation risks.

Frequently Asked Questions about rcode-auth-audit

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

FAQPage Schema
How do I prevent cross-tenant data leakage in a multi-organization Postgres application?

Preventing cross-tenant data leakage requires enforcing tenant_id constraints using Postgres row-level security or middleware. An audit reviews your access patterns and session isolation to ensure multi-tenant data remains restricted to its organization.

Why do users experience ghost sessions or disappear after a Keycloak or Active Directory sync?

Ghost sessions and disappearing users during identity sync usually stem from broken token revocation and missing session invalidation rules. Verifying Keycloak and Active Directory synchronization behavior ensures dynamic JWKS validation and explicit logout protocols are enforced correctly.

How do I audit JWT validation and session lifecycle flows for security gaps?

Auditing JWT validation and session lifecycle flows involves checking login, refresh, logout, and password reset processes for security gaps. A thorough review verifies dynamic JWKS validation, explicit session invalidation, and proper token revocation behavior across all authentication surfaces.

Can I use this to check Postgres row-level security and tenant_id enforcement?

Yes, you can use this to check Postgres row-level security and tenant_id enforcement. It reviews your database access patterns to verify that RLS policies and middleware constraints are actively preventing cross-tenant reads and writes in multi-organization systems.

What is the best way to catch authentication drift before it becomes a production incident?

The best way to catch authentication drift is through periodic sync verification and dynamic JWKS validation. Reviewing identity synchronization behavior, token revocation rules, and session invalidation logic helps identify stale sessions and broken authorization flows before users notice.