Borrowing it
Nothing to install: this file belongs to hypertrial/data-control-center. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hypertrial/data-control-center/main/.agents/skills/pad/SKILL.mdgit clone --depth 1 https://github.com/hypertrial/data-control-centerWrote 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/hypertrial/data-control-center/pad)<a href="https://agentmods.dev/skills/hypertrial/data-control-center/pad"><img src="https://agentmods.dev/badge/skills/hypertrial/data-control-center/pad/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/hypertrial/data-control-center/pad"><img src="https://agentmods.dev/badge/skills/hypertrial/data-control-center/pad.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.00027 | $0.00701 |
| Opus 5.5 | $0.00011 | $0.00280 |
| Sonnet 5.5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
pad 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pad — Talk to Your Project
Use Pad when the user discusses project work: issues, tasks, plans, ideas, progress, dependencies, conventions, roles, standups, or retrospectives.
Load context once per conversation
Before the first Pad action in a conversation, run pad bootstrap --format json.
Reuse that context for later Pad turns in the same workspace. Refresh it only
after switching workspaces, after changing collections/conventions/roles/playbooks,
when Pad reports stale schema/context, or when the user asks for a refresh. Use a
targeted item or dashboard read for changing work state; do not rerun bootstrap
just because the skill was invoked again.
- If
padis missing, ask the user to install it or add it to PATH. - If bootstrap fails, run
pad agent guide context-loadingand follow that section. Never initialize authentication blindly. - In Codex, keep
padas a direct command. Shell redirection such as< filecan prevent a narrow Pad execution rule from matching. For--stdin, stream the body through the process's stdin; if the harness cannot do that, request narrowly scoped permission to run Pad with loopback access. - An underlying
operation not permittedmeans the health probe was sandbox-blocked, not that Pad is down. Retry the same direct command with loopback permission, and do not repeat an ambiguous write until its result is checked. - Follow every body in
conventions. Before meaningful work, inspectconvention_indexand load bodies for the matching trigger. - If
needs_onboardingis true, offer setup and wait for consent. - If roles exist and none was chosen in this conversation, ask once; do not block if the user declines.
Act safely
- Use issue IDs such as
TASK-5, never slugs. - Read an item before updating it. Send only changed fields and include a comment with status changes.
- Read collection schemas instead of guessing field names or terminal statuses.
- Confirm each mutation from the returned object before saying it succeeded.
- Use active playbooks when intent or an invocation slug matches; never run draft or deprecated playbooks unless the user explicitly asks.
- Prefer summary reads and bounded lists. Fetch full bodies only when needed.
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 Changed · -264 lines ed2f02f7577d
- 1mo ago First seen · 336 lines · 27 tokens per session scan A ca56cf1b75c4
pad is a skill published in the GitHub repository hypertrial/data-control-center (4 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 701 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-09-08.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…