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 statusgit 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/status)<a href="https://agentmods.dev/skills/perpetualsoftware/pad/status"><img src="https://agentmods.dev/badge/skills/perpetualsoftware/pad/status/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/status"><img src="https://agentmods.dev/badge/skills/perpetualsoftware/pad/status.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.00013 | $0.00556 |
| Opus 5.5 | $0.00005 | $0.00222 |
| Sonnet 5.5 | $0.00003 | $0.00111 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
status 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 20d 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
Run pad project dashboard --format json. Before presenting results, handle these two
failure modes:
padCLI missing (command not found): say so and point at https://getpad.dev/install. Don't retry or guess at alternate paths.- No
.pad.tomlfound in the directory tree: say this project isn't linked to a Pad workspace yet and suggest/pad:onboard.
If the response's needs_onboarding field is true, lead with the same active offer
the main skill uses — before anything else: "This workspace is brand new and isn't
set up yet. Want me to set it up? I'll ask a few quick questions and adapt it to your
project." This is an offer, not an auto-run; mention /pad:onboard as the shortcut
for later.
Otherwise, present it conversationally: collection summaries, active plan progress, attention items (stalled/overdue), and suggested next actions.
Connection header (show this first, above the dashboard). Also run
pad session status --format json and lead with a one-line connection state, so a user
who types /pad:status after reading the push docs sees whether this session is wired
to Pad's live stream:
announced_armedtrue → "Set to accept pushes (armed)."announced_armedmeans consent is on, NOT that a monitor is connected — so only add a live claim from the server: ifserver_reachableis true, "server seesaccepting_sessionsofconnected_sessionssessions accepting pushes"; if false, "(server not reachable)".local_stateisdisarmedandauto_armis true → "Disconnected this session (auto_arm will re-arm the next session)."local_stateiserror→ "Local push state unreadable — failing closed; run/pad:connectto reset."local_stateisunverifiable→ "This session can't be verified on this platform, so a local connect can't take effect — usepush.auto_armin.pad.toml;pad session resetclears the local override."- otherwise not accepting → "Not accepting pushes — run
/pad:connectto receive them here."
Keep it to one line; it's a header, not the main event. If pad session status fails
(e.g. padd unreachable), skip the header rather than blocking the dashboard.
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.
- 20d ago Changed · +3 lines 4ba58c5b23f4
- 1mo ago First seen · 39 lines · 13 tokens per session scan A 77f438a0bb16
status is a skill published in the GitHub repository PerpetualSoftware/pad (195 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 556 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
daily-brief-loop
Use only when the user explicitly asks to run, sync, advance, or persist Mora's durable daily brief. Executes the once-per-day, human-checkpointed NO-SEND operator loop, performs configured source syncs, writes the dated artifact and run log, and advances the brief watermark.
mora-recall
Retrieve the user's own history before answering questions about their people, projects, meetings, messages, decisions, commitments, or past work. Use for requests such as "what did we discuss", "what did I decide", "what do you know about", "catch me up", and "what changed".
dining-concierge
Use when recommending a restaurant, bar, cafe, happy hour, or other food or drink outing—especially when the request names people the user knows. Grounds live recommendations in task-minimal Mora history before using public web information.
memory-capture
Save durable information to Mora only when the user explicitly asks to remember, save, or capture a fact, decision, insight, or task. Use for governed write-back, not for implicit extraction from ordinary conversation and never for deletion.
haypile
Search the user's local documents (PDF, docx, pptx, markdown, text, HTML, mbox email) through Haypile, a local search daemon. Use when the user asks what their files say, wants passages from contracts, papers, or notes, or wants a folder indexed for search. Every result carries a file and page citation. Runs entirely…
gh-skill
Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment.