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.
npx skills add dan-fetch-studio/tidyports-integrations --skill tidyportsgit clone --depth 1 https://github.com/dan-fetch-studio/tidyports-integrationsWrote 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/dan-fetch-studio/tidyports-integrations/tidyports)<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.
<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>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 | $0.00049 | $0.00378 |
| Sonnet 5 | $0.00020 | $0.00151 |
| Haiku 4.5 | $0.00010 | $0.00076 |
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 10d 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.
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-portsCLI 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-yto 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:
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.
- 10d ago First seen · 62 lines · 99 tokens per session scan A b82ac439142d
tidyports is a skill published in the GitHub repository dan-fetch-studio/tidyports-integrations (0 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 755 once invoked, about $0.0005 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-31.
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…