

Auth and Permissions Checkup
Your agent learns to check sign-up, login, sessions, password reset and who is allowed to see or change what.
Your agent maps every page and endpoint, then checks that each one requires a valid session, that records can only be read or changed by their owner, that passwords are hashed, that sessions and reset links expire, and that login errors and limits give nothing away. It fixes the gaps it can in code and adds missing data access rules in a new migration. It tells you to run a two-window test with two accounts, open protected pages while signed out, confirm that logging out on one device signs out the other, reuse a reset link, and confirm settings in your auth dashboard.
Spend 100 tokens on Auth and Permissions Checkup? You have 350 tokens.
You need 50 more tokens.
Get tokensBought. It's in your Library.
Token purchases are final. Tokens do not expire and can be used at any time.
Your first skill is on us. Every new account starts with 100 welcome tokens.
A look inside
## Standard
Two questions on every request: who is this, and may they do this. A working login screen proves neither. Check what users cannot do, not only what they can. Each check gets a pass or fail with the file that proves it. Fix what is safe to fix in code and report the rest.
## When the builder did not ask for a check
Finish the requested change first and keep it as small as asked. Then run the procedure below across the app as a read-only check. Do not fix, rewrite or delete anything the builder did not ask for, even when the fix looks small and safe. In your reply, say what you built, then list what the check found, most serious first: the problem in plain words, the file, and why it matters to the builder. Then ask the builder whether you should fix them, and stop. Fix only after the builder says go.
## Procedure
First read the whole repository: every page and layout, every API route and server action, the middleware, every migration and database policy, the auth provider setup, the signup, login, logout and reset code, and anywhere a token or cookie is written. Build a list of every route with two columns: needs login, needs ownership or role. Then check all eight.
How to use it
- Download the file.
- Add it to whatever agent you build with.
- Ask your agent to run it.
Checkups also run on their own when your agent works on that layer. If one finds a problem you did not ask about, it tells you and waits for your go before fixing anything.
Learn the method free
This skill comes out of a free course in the community: The Foundation, Layer 4: Auth & Permissions.
Packs that include this skill
All 13 Checkups, one for every layer of your app.
Version 1.0.0 · Last updated November 14, 2026