pbakaus/burn-after-login is an open-source project on GitHub with 52 stars, written primarily in Svelte. Self-destructing skill to solve browser automation login pain.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
"Good morning. Your mission, should you choose to accept it, is to create dev-only auth shortcuts so AI browser agents stop fumbling with your login forms. This skill will self-destruct after completion."
A self-destructing Agent Skill that creates dev-only auth shortcuts for AI browser automation — then removes itself, leaving no trace.
The Problem
AI agents with browser automation (Claude in Chrome, Playwright MCP, agent-browser, Stagehand, Cursor's browser mode...) hit login walls and waste time filling out forms, handling redirects, and losing session state.
The Solution
Install the skill, run it, and it sets up dev-only auth shortcuts tailored to your stack. After setup, your agents can authenticate in one step:
# Browser agents navigate here to get authenticated
http://localhost:3000/[email protected]&password=demo
# Or grab a token for API testing
TOKEN=$(./scripts/get-token [email protected] demo)
How It Works
1. Install the skill
2. Run it — it analyzes your auth system and creates dev-only shortcuts
3. It detects your browser automation tools and updates agent instructions
4. It asks to self-destruct
5. You're left with working auth shortcuts and zero trace of the skill
Install
npx skills add pbakaus/burn-after-login
This installs the skill into your project's .agents/skills/ directory (and symlinks into .claude/skills/ and other tool-specific locations as needed).
Use
In Claude Code:
/burn-after-login
In other compatible agents, invoke the skill per your tool's conventions.
What It Does
Validates your environment has dev mode detection and an auth system
Finds existing dev/test credentials in your codebase
Analyzes how your auth works (tokens, sessions, or both)
Creates dev-only auth shortcuts that match your stack:
Login endpoints for session-based auth
Token generator scripts for API auth
All guarded to return 404 in production
Detects your browser automation tools (Playwright, Puppeteer, Claude in Chrome, Cypress, Stagehand, etc.)
Updates your agent instructions (CLAUDE.md, AGENTS.md, CURSOR.md, etc.) with tool-specific auth examples
Self-destructs — removes itself from your project
Supported Stacks
Works with any combination of:
Languages: Node.js, Python, Ruby, Go, Rust, and more
Frameworks: Next.js, Django, Rails, Flask, FastAPI, Express, and more
Auth: Supabase, NextAuth, Clerk, Firebase, Passport, Devise, custom auth, and more
Browser tools: Claude in Chrome, Playwright MCP, Chrome DevTools MCP, agent-browser, Stagehand, Puppeteer, Cypress, Selenium
Skill Structure
This repo follows the Agent Skills specification:
burn-after-login/
├── SKILL.md # The skill instructions (required by spec)
├── README.md # This file (for the GitHub repo page)
└── LICENSE # MIT
When installed, the skill directory is copied into your project (e.g. .agents/skills/burn-after-login/). After self-destruct, the directory is removed.
Security
Shortcuts only work in development mode — they return 404 in production
Uses your existing auth system — no new attack surface
Never logs credentials
The skill itself leaves no trace after self-destruct
FAQ
Can I run it again?
If you declined self-destruct, yes. If it already self-destructed, just reinstall it.
What if my project doesn't have test users?
The skill will detect this and ask you to create them first.
Does it modify my auth system?
No. It creates new endpoints/scripts that call your existing auth functions.
What files does it create?
Depends on your stack. Typically one route file or script, plus documentation updates. It will show you exactly what it created before self-destructing.
Yes — pbakaus/burn-after-login ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/pbakaus/burn-after-login.
What is pbakaus/burn-after-login?
pbakaus/burn-after-login (pbakaus/burn-after-login) is a Svelte project on GitHub. From the project's own README: Self-destructing skill to solve browser automation login pain.
Where do I read more about pbakaus/burn-after-login?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/pbakaus/burn-after-login is the definitive source.
Read full README in the tab above.
Curious whether burn-after-login is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about burn-after-login.