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 PerpetualSoftware/pad --skill disconnectgit clone --depth 1 https://github.com/PerpetualSoftware/padWrote 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/perpetualsoftware/pad/disconnect)<a href="https://agentmods.dev/skills/perpetualsoftware/pad/disconnect"><img src="https://agentmods.dev/badge/skills/perpetualsoftware/pad/disconnect/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/perpetualsoftware/pad/disconnect"><img src="https://agentmods.dev/badge/skills/perpetualsoftware/pad/disconnect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00018 | $0.00367 |
| Opus 5.5 | $0.00007 | $0.00147 |
| Sonnet 5.5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
disconnect 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 1mo 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.
What it actually says
/pad:disconnect withdraws THIS session's consent to receive pad push notifications.
It holds for the rest of the session even if the repo opted in via
.pad.toml push.auto_arm — a disconnect must not be a lie.
If the pad CLI is missing (command not found), say so and point at
https://getpad.dev/install. Otherwise ALWAYS run the disarm — do NOT gate it on finding
a .pad.toml. Consent is scoped to this SESSION (keyed by the session, not the
workspace), so a session that connected in one repo must be able to disconnect from
anywhere, including a directory with no linked workspace; refusing to disarm there would
leave it receiving pushes.
Steps:
-
Run
pad session disarm. This writes a session-scoped explicit-off marker (it does not delete config), so the session stops accepting pushes now and stays that way for its remaining life. It works regardless of the current directory's workspace. -
Tell the user they're disconnected. If the command reported that the repo has
auto_armon, add the honest caveat: this session is disconnected, but a NEW session in this repo will connect again — to turn that off permanently, removepush.auto_armfrom.pad.toml(the same deliberate edit that turned it on).
Note: the monitor re-checks consent every couple of seconds and drops the open stream
when it sees the disarm, so delivery stops within a brief window rather than lingering.
Run /pad:status to confirm the state.
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.
- 1mo ago First seen · 31 lines · 18 tokens per session scan A c460d0e43179
disconnect is a skill published in the GitHub repository PerpetualSoftware/pad (198 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 367 once invoked, about $0.0001 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-30.
Other skills, from other repositories
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
printing-press
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a…
go
Use when writing, reviewing, testing, or shipping Go code and HTTP services: idioms, %w error wrapping, goroutine/context/errgroup concurrency, net/http 1.22 routing, log/slog, project layout, table-driven tests, Go hardening. NOT language-agnostic threat modeling (that is secure-coding), NOT Dockerfile/CI shipping…
backend-development
Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.
scaffold-project
Scaffold a new app, API, backend, fullstack project, mobile app, polyglot service, monorepo, or starter with Better Fullstack. Use when the user wants to create, start, bootstrap, initialize, or generate a project from a stack description. Prefer the bundled Better Fullstack MCP server: guidance, schema…
rust-conventions
Rust conventions: edition, fmt and clippy, error crates and propagation, unsafe documentation, API naming guidelines, traits, testing, benchmarks, tokio, cargo audit. Use when writing or reviewing Rust code.