Expose Localhost

This is a comprehensive ngrok wrapper that takes the guesswork out of exposing local services to the internet. It'll detect your port from package.json or .env files, ask you upfront about domains and access control, then handle the tunnel setup with optional OAuth, rate limiting, or OWASP protection via Traffic Policy. The workflow is thoughtfully structured to avoid the usual trial and error, getting all your preferences before executing anything. What stands out is the attention to common failure modes, like catching the missing dev domain error and explaining how to fix it. If you regularly demo work to clients or test webhooks, this beats memorizing ngrok flags every time.

skills.sh installs: 273
GitHub stars: 13
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add ngrok/agent-skills --skill expose-localhost --agent claude-code

Installs into .claude/skills of the current project.

Files

Expose Localhost

Expose a local service to the public internet using ngrok. Optionally add OAuth, OWASP protection, or rate limiting via Traffic Policy.

Prerequisites

ngrok CLI installed (ngrok command available)
Auth token configured (ngrok config add-authtoken <TOKEN>)

Workflow

Step 1: Pre-flight & Configuration

Silently verify ngrok is ready:

ngrok config check

If auth token missing, tell user to run: ngrok config add-authtoken <TOKEN> (get token at https://dashboard.ngrok.com/get-started/your-authtoken)

Then ask all questions upfront before doing anything:

Before I expose your service, I need a few details:

1. **Port**: I see your app runs on port 3000. Is that correct?
2. **Domain**: Use your dev domain, or do you have a custom domain?
3. **Access control**: Open access, or require login (Google/GitHub/etc.)?
4. **Save config?**: One-time setup, or save for reuse?

Do NOT mention cloud endpoints, reserved domains, or internal endpoints — those are advanced concepts the user shouldn't need to think about.

SKILL.md on GitHub