p3-data-model

p3-data-model is a command for Claude Code from jonase47/ccpr. It costs 0 tokens per session (2,280 once invoked), scanned A, original, MIT.

A guide for designing a data model—the entities and relationships a system stores—and an API specification—the interfaces other software uses to exchange data.

In plain words
What is it for?
Use it to define database entities, relationships, data flows, and API interfaces for a complete system or a specific domain.
Why use it?
It creates a shared foundation for implementation and connects product features, user journeys, data needs, and privacy requirements.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: reads .claude/ paths.

Good fit Use it to define database entities, relationships, data flows, and API interfaces for a complete system or a specific domain.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/jonase47/ccpr/p3-data-model
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.

Clone the repo
git clone --depth 1 https://github.com/jonase47/ccpr

Made for: Claude Code.

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.

agentmods badge for p3-data-model

README.md
[![agentmods](https://agentmods.dev/badge/commands/jonase47/ccpr/p3-data-model/github.svg)](https://agentmods.dev/commands/jonase47/ccpr/p3-data-model)
Your own site
<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-data-model"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-data-model/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.

agentmods 80×15 button for p3-data-model

Your own site · 80×15
<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-data-model"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-data-model.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,280 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02280
Opus 5.5 $0.00000 $0.00912
Sonnet 5.5 $0.00000 $0.00456
Haiku 4.5 $0.00000 $0.00228

Measured 1mo ago against content hash fe568d11dd8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

p3-data-model 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.

commands/p3-data-model.md · 217 lines

How it starts

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

/p3-data-model – Data Model & API Design

Designs the Data Model with entities and relationships as well as the API design with interface specification. The result is DATA_MODEL.md and API_SPEC.md as the binding foundation for implementation.

Argument: $ARGUMENTS = [Domain/Entity, e.g. "User Management", "Order Process", "Product Catalog"]

If provided: Focus the design on the named domain or entity and its direct relationships. If not provided: Read ARCHITECTURE.md, FEATURES.md and USER_JOURNEYS.md and develop the complete Data Model for the entire system. If any context is missing, ask for the core entities of the system.

Execution

1. Read Context

Read the following files (if available):

  • ARCHITECTURE.md (components, data flows – what must the model support?)
  • TECH_STACK.md (database choice – influences the model design)
  • FEATURES.md (which features impose which data requirements?)
  • USER_JOURNEYS.md (what data is generated during usage?)
  • DSGVO_INITIAL_ASSESSMENT.md (DSGVO (GDPR) privacy constraints: deletability, anonymization)

2. Delegation to System Architect Agent (Lead)

Delegate the Data Model and API design to the system-architekt agent:

Design the Data Model and API specification. Focus (if provided): $ARGUMENTS Context: [insert key points from ARCHITECTURE.md, FEATURES.md, TECH_STACK.md]

A. Data Model

  • Entity-Relationship diagram (Mermaid ERD or ASCII)
  • Per entity: fields with data types, required fields, constraints
  • Relationships: 1:1, 1:n, n:m with justification
  • Indexes: which fields are indexed for performance?
  • DSGVO markings: which fields contain personal data?

B. API Design

  • API style: REST / GraphQL / tRPC – with justification
  • Resources and endpoints (overview of all routes)
  • Request/Response schemas for critical endpoints
  • Authentication and authorization concept at the API level
  • Error handling: standard error codes and formats
  • Versioning strategy

C. Database Design Decisions

  • Normalization level and justification
  • Migration strategy (how are schema changes deployed?)
  • Soft Delete vs. Hard Delete – decision and justification (DSGVO-relevant)
  • Audit trail: which changes are logged?

Read the full file on GitHub · 217 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.

  1. 1mo ago Changed · +1 lines fe568d11dd8d
  2. 1mo ago Changed 383af079a080
  3. 1mo ago First seen · 216 lines · 0 tokens per session scan A b9e5a83f3984

Subscribe to this mod's changes

p3-data-model is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,280 tokens. 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-03.