Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/spencerpauly/awesome-cursor-skills/finding-dev-server-url)<a href="https://agentmods.dev/skills/spencerpauly/awesome-cursor-skills/finding-dev-server-url"><img src="https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/finding-dev-server-url/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/spencerpauly/awesome-cursor-skills/finding-dev-server-url"><img src="https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/finding-dev-server-url.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.00826 |
| Opus 5 | $0.00015 | $0.00413 |
| Sonnet 5 | $0.00006 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
finding-dev-server-url scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- finding-dev-server-url — 92% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finding Dev Server URL
Detect which dev servers are running, what ports they're on, and open them.
How It Works
Cursor stores live terminal output in text files. Each terminal has a file at:
<terminals_folder>/<id>.txt
The terminals folder path is provided in your system context. Each file contains metadata (pid, cwd, last command) followed by the full terminal output.
Workflow
1. List All Terminals
ls <terminals_folder>/*.txt
2. Read Each Terminal's Metadata
Read the first ~10 lines of each terminal file to see:
pid— process IDcwd— working directorylast_command— what's running (e.g.npm run dev,pnpm dev,python manage.py runserver)
Skip terminals where the last command is clearly not a server (e.g. git status, ls, cd).
3. Scan for Server URLs
Read the full content of terminals that look like they're running a server. Search for these patterns:
| Framework | Pattern |
|---|---|
| Next.js | Local: http://localhost:XXXX or ▲ Ready |
| Vite | Local: http://localhost:XXXX/ |
| Create React App | Local: http://localhost:XXXX |
| Express | listening on port XXXX or listening at http://... |
| Django | Starting development server at http://127.0.0.1:XXXX/ |
| Rails | Listening on http://127.0.0.1:XXXX |
| Flask | Running on http://127.0.0.1:XXXX |
| Go | Listening on :XXXX or http server started on :XXXX |
| PHP | Development Server (http://localhost:XXXX) started |
| Remix | http://localhost:XXXX |
| Astro | http://localhost:XXXX |
| Nuxt | http://localhost:XXXX |
Regex to match most server output:
https?://(localhost|127\.0\.0\.1|0\.0\.0\.0)(:\d+)
Also check for standalone port patterns:
(listening|started|running|ready|serving).*(port\s*|:)\s*(\d{4,5})
4. Report
Print a summary:
Dev servers found:
Terminal 1 (pid 12345) — npm run dev → http://localhost:3000 (cwd: /Users/me/app)
Terminal 3 (pid 67890) — python manage.py runserver → http://127.0.0.1:8000 (cwd: /Users/me/api)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 101 lines · 31 tokens per session scan A ee1b5d6b0cfe
finding-dev-server-url is a skill published in the GitHub repository spencerpauly/awesome-cursor-skills (765 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 31 tokens to every session and 826 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…