status

A project-status dashboard that summarizes plans, progress, and items needing attention. It also reports whether the current session is connected to the project’s live update stream.

In plain words
What is it for?
Use it to review collection summaries, active-plan progress, stalled or overdue items, suggested next actions, and session connection status.
Why use it?
It gives a quick view of project health without checking plans, overdue work, and connection details separately.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/perpetualsoftware/pad/status
Any agent
npx skills add PerpetualSoftware/pad --skill status
Clone the repo
git clone --depth 1 https://github.com/PerpetualSoftware/pad

Made for: Claude Code, Codex.

Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 500 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.00500
Opus 5 $0.00006 $0.00250
Sonnet 5 $0.00003 $0.00100
Haiku 4.5 $0.00001 $0.00050

Measured 2d ago against content hash 77f438a0bb16, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

plugin/skills/status/SKILL.md · 39 lines

What it actually says

Run pad project dashboard --format json. Before presenting results, handle these two failure modes:

  • pad CLI missing (command not found): say so and point at https://getpad.dev/install. Don't retry or guess at alternate paths.
  • No .pad.toml found 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_armed true → "Set to accept pushes (armed)." announced_armed means consent is on, NOT that a monitor is connected — so only add a live claim from the server: if server_reachable is true, "server sees accepting_sessions of connected_sessions sessions accepting pushes"; if false, "(server not reachable)".
  • local_state is disarmed and auto_arm is true → "Disconnected this session (auto_arm will re-arm the next session)."
  • local_state is error → "Local push state unreadable — failing closed; run /pad:connect to reset."
  • otherwise not accepting → "Not accepting pushes — run /pad:connect to 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.

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.

  1. 2d ago First seen · 39 lines · 13 tokens per session scan A 77f438a0bb16

Subscribe to this mod's changes

status is a skill published in the GitHub repository PerpetualSoftware/pad (146 stars, last pushed 2d ago), licensed Apache-2.0. It adds 13 tokens to every session and 500 once invoked, about $0.0001 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-30.