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-prdgit 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-prd)<a href="https://agentmods.dev/skills/ljucask/pureinn-product-development/pm-prd"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-prd/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-prd"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-prd.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.00090 | $0.08127 |
| Opus 5 | $0.00045 | $0.04064 |
| Sonnet 5 | $0.00018 | $0.01625 |
| Haiku 4.5 | $0.00009 | $0.00813 |
Grade A, and why
pm-prd 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 10d 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 — 769 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM - Product Requirements Document (PRD)
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.
Artifact language
Checks state.json → artifact_language. Default (unset or "English"): no change in behavior.
- If set to a non-English language: write the PRD's prose (problem statement, rationale, Business Capability descriptions, narrative sections) in that language.
- Never translate:
FEAT-ID/BR-IDreferences, frontmatter keys and enum values, section headers (## Business Capabilities, etc.), file names - these stay English always, regardless of the setting.
What this skill does
Two modes - detected automatically in Step 0:
| Mode | Context | Inputs | Output | Frozen? |
|---|---|---|---|---|
| Product PRD | Greenfield Phase 3b | All Phase 2+3a+3b outputs | product/PRD_master.md |
Yes - frozen after creation |
| Initiative PRD | Feature Implementation after Track B | initiatives/[slug]/discovery/ |
initiatives/[slug]/prd.md |
No - living for that initiative |
Product PRD_master is the original product scope document. It does NOT change after creation. New scope, new functionality, changed assumptions → new Initiative PRD for that initiative. PRD_master remains as the stable historical record.
Initiative PRD is a leaner document scoped to one domain/initiative. It contains Business Capabilities for that domain only - the entry point for pm-entity-registry (append mode), pm-business-rules-library (append mode), and pm-features-list (FI append mode) for this initiative.
Product PRD synthesizes all Phase 2, Phase 3a, and Phase 3b outputs into a single coherent product-level document:
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.
- 10d ago First seen · 769 lines · 90 tokens per session scan A 3651c47c79d9
pm-prd is a skill published in the GitHub repository ljucask/pureinn-product-development (2 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 8,127 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
ddt-baseline-sync
A skill that imports staffing, work-hour, or project-plan spreadsheets and CSV files into a historical project baseline. A baseline is past project data used to improve future work-hour estimates.
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
chief-information-officer
The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
chief-operating-officer
Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…
head-of-pmo
The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. Use this to stand up or reform a PMO, decide what it should and should not control, judge whether it is adding value or overhead, or work out why teams route around it.