Skip to main content
skill CX Codex

supabase-extract-url — Claude Code skill: setup and features

supabase-extract-url extracts the Supabase project URL from frontend JavaScript bundles, meta tags, and local app configs.

MIT 506 installs ★ 76 updated 2026-01-31

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add yoanbernabeu/supabase-pentest-skills --skill supabase-extract-url -a claude-code
Open on GitHub

What supabase-extract-url does

This skill scans client-side assets to identify Supabase project URLs. It inspects environment variables like VITE_SUPABASE_URL or NEXT_PUBLIC_SUPABASE_URL, direct createClient calls, and HTML tags. The tool flags standard domains, regional endpoints, and custom domain patterns.

Discovered endpoints undergo format verification and a REST reachability check. The skill writes findings immediately to .sb-pentest-context.json and records every step in .sb-pentest-audit.log, protecting progress against interruptions.

Running this requires access to the live target URL or downloaded asset directory. Finding an endpoint reveals API routes, but actual testing still demands an API key.

What it helps with

  • locate Supabase project URLs in compiled JavaScript chunks
  • verify target REST API reachability during security testing
  • export extracted endpoints and project identifiers to a context file

Example prompts for the agent

  • Extract the Supabase URL from downloaded files in ./dist/assets/
  • Scan client scripts at https://myapp.example.com to find the Supabase backend URL
  • Run a deep scan to discover Supabase endpoints on https://myapp.example.com

How to install supabase-extract-url

1Skills CLI (Vercel)

npx skills add yoanbernabeu/supabase-pentest-skills --skill supabase-extract-url -a claude-code

2Manually: put the files in place

~/.claude/skills/supabase-extract-url/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/supabase-extract-url/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about supabase-extract-url

How to install supabase-extract-url in Claude Code?

Run npx skills add yoanbernabeu/supabase-pentest-skills --skill supabase-extract-url -a claude-code in your terminal.

What does supabase-extract-url do?

It parses web application assets to find Supabase backend URLs, checks endpoint responses, and extracts project references.

Where does the skill store its findings?

Discovered URLs and endpoints are saved in .sb-pentest-context.json, while actions are logged to .sb-pentest-audit.log.

Source text

SKILL.md · MIT
---
name: supabase-extract-url
description: Extract the Supabase project URL from client-side JavaScript code, environment variables, and configuration files.
---

# Supabase URL Extraction

> 🔴 **CRITICAL: PROGRESSIVE FILE UPDATES REQUIRED**
>
> You MUST write to context files **AS YOU GO**, not just at the end.
> - Write to `.sb-pentest-context.json` **IMMEDIATELY after each discovery**
> - Log to `.sb-pentest-audit.log` **BEFORE and AFTER each action**
> - **DO NOT** wait until the skill completes to update files
> - If the skill crashes or is interrupted, all prior findings must already be saved
>
> **This is not optional. Failure to write progressively is a critical error.**

This skill extracts the Supabase project URL from a web application's client-side code.

## When to Use This Skill

- After detecting Supabase usage, to get the exact project URL
- When you need the API base URL for further testing
- To identify which Supabase project an application uses

## Prerequisites

- Target URL accessible
- Supabase usage detected (or suspected)

## How It Works

The skill scans for URL patterns in:

### 1. JavaScript Source Code

```javascript
// Direct URL references
const SUPABASE_URL = 'https://abc123.supabase.co'
createClient('https://abc123.supabase.co', key)

// Environment variable patterns
process.env.SUPABASE_URL
process.env.NEXT_PUBLIC_SUPABASE_URL
import.meta.env.VITE_SUPABASE_URL
```

### 2. HTML Meta Tags and Scripts

```html
<meta name="supabase-url" content="https://abc123.supabase.co">
<script>
  window.SUPABASE_URL = 'https://abc123.supabase.co'
</script>
```

### 3. Configuration Objects

```javascript
const config = {
  supabase: {
    url: 'https://abc123.supabase.co'
  }
}
```

## URL Pattern Matching

Recognized patterns:

| Pattern | Example |
|---------|---------|
| Standard | `https://abc123.supabase.co` |
| With region | `https://abc123.eu-central-1.supabase.co` |
| Custom domain | Detected via API endpoint patterns |

## Usage

### Basic Extraction

```
Extract Supabase URL from https://myapp.example.com
```

### From Local Files

If you have downloaded the source:
```
Extract Supabase URL from ./dist/assets/
```

## Output Format

```
═══════════════════════════════════════════════════════════
 SUPABASE URL EXTRACTED
═══════════════════════════════════════════════════════════

 Project URL: https://abc123def.supabase.co
 Project Ref: abc123def
 Region: us-east-1 (inferred)

 Found in:
 ├── /static/js/main.abc123.js (line 1247)
 │   └── const SUPABASE_URL = 'https://abc123def.supabase.co'
 │
 └── /static/js/chunk.def456.js (line 89)
     └── createClient('https://abc123def.supabase.co', ...)

 API Endpoints:
 ├── REST API: https://abc123def.supabase.co/rest/v1/
 ├── Auth API: https://abc123def.supabase.co/auth/v1/
 ├── Storage: https://abc123def.supabase.co/storage/v1/
 └── Realtime: wss://abc123def.supabase.co/realtime/v1/

 Context updated: .sb-pentest-context.json
═══════════════════════════════════════════════════════════
```

## Context Output

Saved to `.sb-pentest-context.json`:

```json
{
  "supabase": {
    "project_url": "https://abc123def.supabase.co",
    "project_ref": "abc123def",
    "region": "us-east-1",
    "endpoints": {
      "rest": "https://abc123def.supabase.co/rest/v1/",
      "auth": "https://abc123def.supabase.co/auth/v1/",
      "storage": "https://abc123def.supabase.co/storage/v1/",
      "realtime": "wss://abc123def.supabase.co/realtime/v1/",
      "functions": "https://abc123def.supabase.co/functions/v1/"
    },
    "sources": [
      {
        "file": "/static/js/main.abc123.js",
        "line": 1247,
        "context": "const SUPABASE_URL = 'https://abc123def.supabase.co'"
      }
    ]
  }
}
```

## Multiple URLs

If multiple Supabase URLs are found:

```
═══════════════════════════════════════════════════════════
 MULTIPLE SUPABASE URLS FOUND
═══════════════════════════════════════════════════════════

 ⚠️  Multiple Supabase projects detected

 1. https://abc123.supabase.co (primary - most references)
    └── Found in: main.js, config.js

 2. https://xyz789.supabase.co (secondary)
    └── Found in: analytics.js

 Using primary URL for further analysis.
 To use a different URL, specify it manually.
═══════════════════════════════════════════════════════════
```

## Validation

The skill validates extracted URLs by:

1. **Format check** — Matches expected Supabase URL patterns
2. **Reachability check** — Attempts to reach the REST API endpoint
3. **Response validation** — Confirms Supabase-like response

```
Validation:
├── Format: ✅ Valid Supabase URL format
├── Reachable: ✅ REST API responds (200 OK)
└── Confirmed: ✅ Response matches Supabase pattern
```

## Common Issues

❌ **Problem:** URL not found despite Supabase detection
✅ **Solution:** The URL may be in a dynamically loaded chunk. Try:
```
Extract URL with deep scan from https://myapp.example.com
```

❌ **Problem:** URL found but validation fails
✅ **Solution:** The project may be paused or the region may have connectivity issues. The URL is still recorded.

❌ **Problem:** Only custom domain found
✅ **Solution:** Custom domains are valid. The skill will note it as a custom domain and attempt to identify the underlying project.

## Security Notes

- This skill only reads publicly available code
- No authentication is attempted
- The URL alone does not grant access (key is also required)

## Next Steps

After extracting the URL:
1. Run `supabase-extract-anon-key` to find the API key
2. Run `supabase-extract-service-key` to check for leaked service keys
3. Proceed to API auditing skills

## MANDATORY: Progressive Context File Updates

⚠️ **This skill MUST update tracking files PROGRESSIVELY during execution, NOT just at the end.**

### Critical Rule: Write As You Go

**DO NOT** batch all writes at the end. Instead:

1. **Before starting any action** → Log the action to `.sb-pentest-audit.log`
2. **After each discovery** → Immediately update `.sb-pentest-context.json`
3. **After each significant step** → Log completion to `.sb-pentest-audit.log`

This ensures that if the skill is interrupted, crashes, or times out, all findings up to that point are preserved.

### Required Actions (Progressive)

1. **Update `.sb-pentest-context.json`** with extracted data:
   ```json
   {
     "supabase": {
       "project_url": "https://[ref].supabase.co",
       "project_ref": "[ref]",
       "endpoints": { ... }
     }
   }
   ```

2. **Log to `.sb-pentest-audit.log`**:
   ```
   [TIMESTAMP] [supabase-extract-url] [START] Beginning URL extraction
   [TIMESTAMP] [supabase-extract-url] [SUCCESS] URL extracted: https://[ref].supabase.co
   [TIMESTAMP] [supabase-extract-url] [CONTEXT_UPDATED] .sb-pentest-context.json updated
   ```

3. **If files don't exist**, create them before writing.

**FAILURE TO UPDATE CONTEXT FILES IS NOT ACCEPTABLE.**

## MANDATORY: Evidence Collection

📁 **Evidence Directory:** `.sb-pentest-evidence/02-extraction/`

### Evidence Files to Create

| File | Content |
|------|---------|
| `extracted-url.json` | URL extraction details with source locations |

### Evidence Format

```json
{
  "evidence_id": "EXT-URL-001",
  "timestamp": "2025-01-31T10:05:00Z",
  "category": "extraction",
  "type": "url_extraction",

  "extracted_data": {
    "project_url": "https://abc123def.supabase.co",
    "project_ref": "abc123def",
    "region": "us-east-1"
  },

  "sources": [
    {
      "file": "/static/js/main.js",
      "line": 1247,
      "context": "const SUPABASE_URL = 'https://abc123def.supabase.co'"
    }
  ],

  "endpoints_discovered": {
    "rest": "https://abc123def.supabase.co/rest/v1/",
    "auth": "https://abc123def.supabase.co/auth/v1/",
    "storage": "https://abc123def.supabase.co/storage/v1/",
    "realtime": "wss://abc123def.supabase.co/realtime/v1/"
  }
}
```

## Related Skills

- `supabase-detect` — Detect Supabase usage first
- `supabase-extract-anon-key` — Extract the anon key
- `supabase-extract-service-key` — Check for service key leaks

© yoanbernabeu · MIT · yoanbernabeu/supabase-pentest-skills

Similar skills

All skills for Security →

From the same set24

The whole set →
supabase-extract-service-key supabase-extract-service-key scans client-side bundles and source maps for leaked Supabase service_role keys. Useful during security reviews to prevent RLS bypass. CX Codex +1 519installs supabase-audit-buckets-list supabase-audit-buckets-list is a Claude Code skill that inventories Supabase storage buckets and examines their settings. It runs during storage security audits and access reviews. CX Codex +1 518installs supabase-audit-auth-signup supabase-audit-auth-signup is a Claude Code skill that tests Supabase signup security, checking email validation, password rules, rate limits, and information disclosure. CX Codex +1 517installs supabase-audit-buckets-read supabase-audit-buckets-read is a Claude Code skill that tests file access in Supabase Storage buckets. It runs after bucket discovery to check permissions and spot exposed files. CX Codex +1 516installs supabase-report-compare supabase-report-compare diffs two Supabase security audit reports and sorts every finding into fixed, still open, or new. Useful after a round of fixes and for periodic reviews. CX Codex +1 509installs supabase-extract-jwt The supabase-extract-jwt skill finds Supabase JWTs in client code, cookies, and storage patterns, then inspects their claims. Use it when checking exposed credentials. CX Codex +1 505installs supabase-audit-authenticated supabase-audit-authenticated — a skill for Claude Code, Codex, Cursor, and other platforms that creates a test user and checks what authenticated requests expose versus anonymous ones in Supabase. CX Codex +1 463installs supabase-evidence supabase-evidence is a Claude Code skill that organizes evidence collection for Supabase security tests, saving findings as the audit progresses. CX Codex +1 299installs

Project sponsors

Companies that keep this analytics open