Agent skill · Backend & API

southwest

Search Southwest Airlines fares and points pricing via Patchright browser automation. SW is not in any GDS or API. Covers all fare classes, Companion Pass value, and fare drop monitoring.

borskigithub.com/borskiGitHub ↗
claude-coderead-onlyships scriptsMIT
Install
npx skills add borski/travel-hacking-toolkit --skill southwest --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 15 KB
Bundled scripts: yes
Allowed tools: Bash(python3*)Bash(docker*)
Path: plugins/travel-hacking-toolkit/skills/southwest/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 611
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Southwest Airlines Search Search southwest.com via Patchright (undetected Playwright fork). Southwest is the only major US airline not in any GDS, API, or flight search tool. This skill is the only way to get SW-specific data: fare classes, points pricing, and Companion Pass qualification. **Requires Patchright** (undetected Playwright fork). Standard Playwright and agent-browser are detected and blocked by SW. Patchright patches the browser fingerprint to bypass detection. **Must run headed (headless=False).** SW detects headless browsers even with Patchright. On macOS, a Chrome window briefly appears and closes. For background operation with no popup, use Docker: ```bash # Search new flights (default, no login needed) docker run --rm ghcr.io/borski/sw-fares --origin SJC --dest DEN --depart 2026-05-15 docker run --rm ghcr.io/borski/sw-fares --origin SJC --dest DEN --depart 2026-05-15 --return 2026-05-18 --points --json # Check existing reservation for price drops (requires SW login) docker run --rm -e SW_USERNAME -e SW_PASSWORD \ ghcr.io/borski/sw-fares change --conf ABC123 --first Jane --last Doe --json # List all upcoming trips docker run --rm -e SW_USERNAME -e SW_PASSWORD \ g

What's inside
Steps it walks through
  1. Prerequisites
  2. When to Use
  3. When NOT to Use
  4. Southwest Fare Classes
  5. Companion Pass CPP Formula
  6. Search: Use the Script
  7. How the Script Works
  8. Output Format
  9. Cash Prices
  10. Points Prices
  11. After Tables
  12. Troubleshooting
  13. Limitations
  14. Change Flight Price Monitor (checkchange.py)
Ships with 5 files
  • Dockerfile
  • scripts/check_change.py
  • scripts/entrypoint.sh
  • scripts/monitor.py
  • scripts/search_fares.py
Commands it runs
Search new flights (default, no login needed)
docker run --rm ghcr.io/borski/sw-fares --origin SJC --dest DEN --depart 2026-05-15
docker run --rm ghcr.io/borski/sw-fares --origin SJC --dest DEN --depart 2026-05-15 --return 2026-05-18 --points --json
Check existing reservation for price drops (requires SW login)
docker run --rm -e SW_USERNAME -e SW_PASSWORD \
ghcr.io/borski/sw-fares change --conf ABC123 --first Jane --last Doe --json
List all upcoming trips
ghcr.io/borski/sw-fares change --list --json
Build locally
docker build -t sw-fares skills/southwest/
More from travel-hacking-toolkit
All skills →
About this skill
What does the southwest skill do?

Search Southwest Airlines fares and points pricing via Patchright browser automation. SW is not in any GDS or API. Covers all fare classes, Companion Pass value, and fare drop monitoring.

How do I install it?

Run `npx skills add borski/travel-hacking-toolkit --skill southwest --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From borski/travel-hacking-toolkit, a repository with 611 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going