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.
git clone --depth 1 https://github.com/m4cd4r4/PortPilotWrote 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/plugins/m4cd4r4/portpilot/plugin)<a href="https://agentmods.dev/plugins/m4cd4r4/portpilot/plugin"><img src="https://agentmods.dev/badge/plugins/m4cd4r4/portpilot/plugin/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/plugins/m4cd4r4/portpilot/plugin"><img src="https://agentmods.dev/badge/plugins/m4cd4r4/portpilot/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
portpilot 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 today.
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.
What it actually says
{
"name": "portpilot",
"version": "3.9.1",
"description": "Start and stop dev servers through PortPilot, so Claude reuses a running server instead of starting a second one on a taken port.",
"author": {
"name": "Macdara Ó Murchú"
},
"license": "MIT",
"homepage": "https://github.com/m4cd4r4/PortPilot",
"repository": "https://github.com/m4cd4r4/PortPilot",
"supportUrl": "https://github.com/m4cd4r4/PortPilot/issues",
"types": "./types/index.d.ts"
}
What it installs
The manifest is a name and a version. 1 skill, 1 MCP server travel with it, and installing the plugin installs all of them — 66 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- today Changed 7fc006ba983f
- yesterday Changed dbee8a405585
- 2d ago Changed 6e92b5dd66e6
- 3d ago Changed b7975637cc0f
- 6d ago Changed d63406d7d415
- 8d ago Changed · +1 lines 237b9cf61900
- 9d ago First seen · 13 lines scan A c53825e0437e
portpilot is a plugin published in the GitHub repository m4cd4r4/PortPilot (16 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-07.
Other plugins, from other repositories
humanizer
Remove signs of AI-generated writing from text, making it sound more natural and human. Based on Wikipedia's "Signs of AI writing" guide.
persona
Switchable response personas with a shared token-reduction engine: bundled characters (holmes, genshijin, noctis, lunafreya, ignis), user-defined characters that survive plugin updates, three compression levels persisted across sessions, a persona-switch CLI other skills can call, character-agnostic…
team-comms
Asynchronous discussion between each team member's coding agent over a shared folder (Google Drive, OneDrive, file server). Immutable append-only threads make write conflicts structurally impossible; research is shared as attachments instead of hand-delivered documents; notifications are opt-in per working directory…
agent-ops
Run agents in a terminal multiplexer: herdr and Zellij setup, handoff between agents, role-based teams, persistent sidekicks, and the WSL/VS Code launch doctor. Install at user scope to make it available across all projects.
authoring
Author text deliverables and deliver them: README / CLAUDE.md / release notes / work logs, and posting the result to Slack. Visual deliverables — slide decks, HTML documents and PDF export — live in the visuals plugin. Install at user scope to make it available across all projects.
claude-tooling
Extend and maintain Claude Code itself: slash commands, skill authoring and installation, Desktop routines, plus the SessionStart plugin-update notice. Install at user scope to make it available across all projects.