What is prd-05-page-interaction?

A product-specification tool that turns feature flows into page and interaction requirements. It describes information priority, component behavior, button states, and user messages without designing the visual style.

Use it to specify pages, components, disabled-button reasons, confirmations, and copy for different interaction outcomes.

It gives designers and frontend developers clear behavior to implement, including loading, empty, success, and error cases.

prd-05-page-interaction — Skill for Claude Code and Codex by baobao233

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.

Any agent

npx skills add baobao2333/prd-agent-kit --skill prd-05-page-interaction

Clone the repo

git clone --depth 1 https://github.com/baobao2333/prd-agent-kit

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/baobao2333/prd-agent-kit/prd-05-page-interaction/github.svg)](https://agentmods.dev/skills/baobao2333/prd-agent-kit/prd-05-page-interaction)

Your own site

<a href="https://agentmods.dev/skills/baobao2333/prd-agent-kit/prd-05-page-interaction"><img src="https://agentmods.dev/badge/skills/baobao2333/prd-agent-kit/prd-05-page-interaction/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/baobao2333/prd-agent-kit/prd-05-page-interaction"><img src="https://agentmods.dev/badge/skills/baobao2333/prd-agent-kit/prd-05-page-interaction.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 574 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00061	$0.00574
Opus 5	$0.00030	$0.00287
Sonnet 5	$0.00012	$0.00115
Haiku 4.5	$0.00006	$0.00057

Measured 9d ago against content hash 5266eace9d98, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

prd-05-page-interaction 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 9d 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.

skills/prd-05-page-interaction/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PRD Page Interaction

Purpose

Describe what each page or component must communicate and how it behaves. This skill supports design and frontend development without pretending to replace design work.

Inputs

Flow model.
Rule model.
Known product pages or entry points.

Process

Identify required pages, modules, or components.
Define information hierarchy for each.
Define visible fields and their source meaning.
Define button states and disabled reasons.
Define copy for success, failure, empty, loading, and confirmation states.
Identify interactions that need design attention.

Interaction writing rules

Do not specify pixel-perfect UI unless provided by the user.
Do not invent visual style.
Do specify information priority, state, and user feedback.
Each button must have enabled, disabled, loading, success, and failure behavior when relevant.
Each empty state must explain why it is empty and what the user can do next, if anything.

Output format

# 04 Page & Interaction Spec: {Feature Name}

## 1. Page / component list
| Page or component | Purpose | Entry | Depends on rule / state |
|---|---|---|---|

## 2. Page spec
### {Page Name}

#### Purpose
{What this page helps the user understand or do}

#### Information hierarchy
| Priority | Content | Notes |
|---|---|---|

#### Fields
| Field | Meaning | Display condition | Empty / abnormal display |
|---|---|---|---|

#### Actions
| Action | Enabled condition | Disabled condition | Success result | Failure result |
|---|---|---|---|---|

#### States
| State | Display | User can do |
|---|---|---|
| Loading |  |  |
| Empty |  |  |
| Normal |  |  |
| Error |  |  |
| No permission |  |  |
| Expired / ended |  |  |

#### Copy
| Scenario | Copy | Notes |
|---|---|---|

## 3. Design attention points
| Point | Why it matters | Required decision |
|---|---|---|

## 4. Handoff to next stage
Recommended next skill: `prd-06-admin-config`

Definition of done

The page spec is complete when design knows what must be represented and frontend knows what states must be implemented.

Read the full file on GitHub · 87 lines

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.

9d ago First seen · 87 lines · 61 tokens per session scan A 5266eace9d98

Subscribe to this mod's changes

prd-05-page-interaction is a skill published in the GitHub repository baobao2333/prd-agent-kit (5 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 574 once invoked, about $0.0003 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-31.

Design and UX Planning

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

prd-05-page-interaction