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.
npx skills add ljucask/pureinn-product-development --skill pm-entity-registrygit clone --depth 1 https://github.com/ljucask/pureinn-product-developmentWrote 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/ljucask/pureinn-product-development/pm-entity-registry)<a href="https://agentmods.dev/skills/ljucask/pureinn-product-development/pm-entity-registry"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-entity-registry/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/ljucask/pureinn-product-development/pm-entity-registry"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-entity-registry.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.00098 | $0.03769 |
| Opus 5 | $0.00049 | $0.01885 |
| Sonnet 5 | $0.00020 | $0.00754 |
| Haiku 4.5 | $0.00010 | $0.00377 |
Grade A, and why
pm-entity-registry 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 12d 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM - Entity Registry
Agent mode (--agent)
Supports --agent: runs autonomously in a subagent, drafts the artifact from existing inputs, and returns a short summary + coverage note.
- No flag → interactive (default); if inputs are heavy, offer agent mode.
--agent→ obey. First check inputs are complete. Anything missing: do NOT invent it - mark[ASSUMED - what/why]in the output and summary. Never hallucinate to fill a gap.
What this skill does
Builds Live Register 1 of 4: the Entity & State Registry (/domain/entities.md).
This register is the architectural foundation of the FDD+SDD framework. It defines:
- What business objects exist in the system
- What states each object can be in
- What transitions are allowed between states (including triggers and emitted events)
- Guard conditions are added JIT in Phase 6 (pm-feature-design) - not here
Position in the 4-register architecture:
| Register | File | Content |
|---|---|---|
| 1. Entity & State Registry | /domain/entities.md |
Domain objects + state machines (THIS SKILL) |
| 2. Business Rules Library | /domain/business_rules.md |
Business rules catalog (pm-business-rules-library) |
| 3. Decision Models Matrix | /domain/decision_models.md |
Decision tables (pm-business-rules-library) |
| 4. FDD Feature List | /features/feature_list.md |
Feature hierarchy + planning (pm-features-list) |
Source: PRD Business Capabilities section - or product/scope_brief.md Business Capabilities section on commissioned builds (same table contract; the Scope Brief's [CANDIDATE-BR] edge cases additionally seed the rules register). AI extracts nouns from capabilities → entities. State machines reflect the business lifecycle of each entity.
Domain overview diagram: Generated in Excalidraw (high-level visual for the team). State machines per entity: Mermaid.js (embedded in entities.md - readable by Claude Code).
Reconciled mode (when run by pm-reconcile)
If reconcile/reconciliation_report.md exists, it is the authoritative input - use it instead of a naive extraction. Code is truth for structure and naming; the old docs' business meaning is already reconciled into the report. Carry the report's resolved entities, attributes, and state machines plus any flagged divergences; do not re-derive or re-question what the report already settled.
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.
- 12d ago First seen · 392 lines · 98 tokens per session scan A 17dde307db59
pm-entity-registry is a skill published in the GitHub repository ljucask/pureinn-product-development (2 stars, last pushed 2d ago), licensed MIT. It adds 98 tokens to every session and 3,769 once invoked, about $0.0005 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.
Other skills, from other repositories
ai-native-design
A workflow for turning a product brief and API contract into frontend design prompts and implementation guidance. It supports three outside design channels and keeps generated frontend work aligned with the same brief and contract.
backend-development
A set of instructions for building server-side code such as APIs and database-backed applications. It uses API contracts, data models, the chosen technology stack, and tests as the project’s reference points.
decision-gate
A decision checkpoint for software-project workflows. After each phase produces its files, it asks the user to accept the result, request a change, add information, or regenerate it before the next phase begins.
frontend-development
A set of instructions for building the user-facing part of a web application, such as its pages, controls, and interactions. It applies to single-page applications and follows the project’s API, product, technology, and design documents.
relay
A Chinese-language procedure for handing an unfinished task from one AI session to another without losing its context.
validation-loop
A development routine that checks each important file immediately after it is changed by running the project’s build, lint, type-check, or test commands.