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-engineering/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-engineering)<a href="https://agentmods.dev/skills/hypertrial/data-control-center/pad-engineering"><img src="https://agentmods.dev/badge/skills/hypertrial/data-control-center/pad-engineering/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-engineering"><img src="https://agentmods.dev/badge/skills/hypertrial/data-control-center/pad-engineering.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.00032 | $0.00634 |
| Opus 5 | $0.00016 | $0.00317 |
| Sonnet 5 | $0.00006 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
pad-engineering 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 yesterday.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pad Engineering
Use this skill for non-trivial local agentic engineering. Keep Pad's official pad skill for CLI/MCP mechanics. This skill overrides routing that would create Ideas or Tasks.
Git owns code. CI owns verification. Pad owns intent, scope, status, dependencies, decisions, evidence, and handoffs.
Collections
Use only:
work— Feature, Bug, Refactor, Investigation, Maintenanceplans— multi-ticket containers only
Never create Ideas, Tasks, Docs-as-tickets, chores, or extra default types unless the user is explicitly asking for a document. Do not run onboard.
Machine status values: backlog, ready, in-progress, blocked, review, done.
Risk: r0, r1, r2, r3.
Always pass --workspace <slug> from .pad.toml. Always reference items by issue ID.
Ticket body
New Work items MUST start from the canonical Work template. Plans use the Plan template. Required sections must be filled before ready. Dependencies are Pad blocked-by / blocks links, not a prose status field.
Before changing status, lint the ticket:
python3 -m pad_universal lint --ref WORK-1 --workspace <slug>
If the pad-universal package is not on PYTHONPATH, run the same linter from the pad-universal checkout. A ticket that fails the linter is not ready or done.
Lifecycle
- Specify until
ready(playbookspecify) - Reproduce or add failing coverage when practical
- Implement the smallest coherent change (
implement) scripts/verify-fastthenscripts/verify- Independent adversarial review for r2/r3 (
review) - Fix findings and re-verify
- Record evidence (
evidence) or a handoff (handoff)
Do not begin material implementation before the ticket is ready.
Routing
- "new feature/bug/refactor/investigation/maintenance" → create Work with the matching
type - "plan this" / multi-ticket objective → create Plan, then
decomposeinto Work - "what's ready?" →
pad item list work --status ready --workspace <slug> - Do not treat
pad project readyas the Ready gate - Status changes always include
--commentexplaining why
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.
- yesterday First seen · 67 lines · 32 tokens per session scan A 07b6a8d22558
pad-engineering is a skill published in the GitHub repository hypertrial/data-control-center (5 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 634 once invoked, about $0.0002 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-09-08.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.