A command-line tool for seeing which local development servers are using which ports, branches, or worktrees, and for stopping them.

It is for checking what is running, finding who owns a port, stopping an earlier server, and reserving a free port.

It helps identify port conflicts and stray servers without changing the application's port settings.

tidyports — Skill for Claude Code and Codex by dan-fetch-studio

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add dan-fetch-studio/tidyports-integrations --skill tidyports

Clone the repo

git clone --depth 1 https://github.com/dan-fetch-studio/tidyports-integrations

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dan-fetch-studio/tidyports-integrations/tidyports/github.svg)](https://agentmods.dev/skills/dan-fetch-studio/tidyports-integrations/tidyports)

Your own site

<a href="https://agentmods.dev/skills/dan-fetch-studio/tidyports-integrations/tidyports"><img src="https://agentmods.dev/badge/skills/dan-fetch-studio/tidyports-integrations/tidyports/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/dan-fetch-studio/tidyports-integrations/tidyports"><img src="https://agentmods.dev/badge/skills/dan-fetch-studio/tidyports-integrations/tidyports.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 755 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00099	$0.00755
Opus 5.5	$0.00040	$0.00302
Sonnet 5.5	$0.00020	$0.00151
Haiku 4.5	$0.00010	$0.00076

Measured 2mo ago against content hash b82ac439142d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tidyports 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 2mo 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.

skills/tidyports/SKILL.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

TidyPorts: see and kill local dev servers

Drives the tidy-ports CLI so you can inspect and stop local dev servers without the user leaving the chat. These are the same commands the TidyPorts menu-bar app runs, so anything you do here shows up there too.

When a bind fails with EADDRINUSE, ask who has it before touching any code:

tidy-ports who 3000
# :3000 is held by Claude Code, in Ghostty [PID 12345] in checkout (feature/auth-refactor)

Exit 0 means held, 4 means free. If the owner is one of your own earlier runs, stop that one; otherwise take a different port with tidy-ports alloc. Do not edit the application's port configuration to work around a conflict — the binding is not the bug.

First, check it's installed: run command -v tidy-ports. If it's missing, don't guess at alternatives and don't fall back to lsof/kill — stop and tell the user this, verbatim:

TidyPorts isn't installed — it provides the tidy-ports CLI this skill needs. Get it at https://tidyports.app/download, or run: brew install --cask dan-fetch-studio/tap/tidyports (free, macOS 15+). Then ask me again.

All commands are agent-friendly: prefix with TP_NO_COLOR=1, no interactive prompts on the read paths, and the result (URL / data) is printed on stdout while progress goes to stderr.

See what's running

tidy-ports ls — every listening dev port with owner, git branch, uptime, and idle hints (human-readable). Use it to answer "what's running?", "which server is on :3001?", "which worktree is serving this?".
tidy-ports json — the full structured snapshot; use when you need to parse fields.

Kill a stray server

One port: tidy-ports portless kill <port>.
The whole detected dev stack: tidy-ports stop (it confirms first; add -y to skip).

If which server to kill is ambiguous, run tidy-ports ls first and confirm with the user.

Avoid port collisions (parallel agents / worktrees)

When two agents or worktrees spin up servers, they collide on the same port and the process crashes with EADDRINUSE — and an agent often can't tell that apart from a real bug. Before starting a dev server, claim a stable free port for this worktree:

Read the full file on GitHub · 62 lines

Changes

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.

2mo ago First seen · 62 lines · 99 tokens per session scan A b82ac439142d

Subscribe to this mod's changes

tidyports is a skill published in the GitHub repository dan-fetch-studio/tidyports-integrations (0 stars, last pushed 3mo ago), licensed MIT. It adds 99 tokens to every session and 755 once invoked, about $0.0004 per session on Opus 5.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-31.

DevOps and cloud

tidyports next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
tidyportsdan-fetch-studio/tidyports-integrations	Skill	0	3mo ago	MIT	A	99	Claude Code, Codex
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	yesterday	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	yesterday	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code