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.08308 |
| Opus 5.5 | $0.00036 | $0.03323 |
| Sonnet 5.5 | $0.00018 | $0.01662 |
| Haiku 4.5 | $0.00009 | $0.00831 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 778 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.
Standalone run
Needs the artifacts listed under Dependencies - it synthesizes them, so without them there is nothing to synthesize.
- No workspace, or inputs missing: name which are missing and what each one unlocks, then offer the PREREQ paths - proceed on stated assumptions marked
[ASSUMED - what/why], or route to the skill that produces the missing input. Never hard-block, and never invent the input. - Writing never depends on
/pureinnhaving run: with no workspace, create just the folder this skill writes into, or write to a path the user names, and say where the file went. - Read
pureinn-variables.md/state.jsonwhere a value is actually used, not at the top of the run. Missing value: continue and name the capability it costs.
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 |
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.
- 1mo ago Changed · +9 lines e44499fa079c
- 1mo 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 19d ago), licensed MIT. It adds 90 tokens to every session and 8,308 once invoked, about $0.0004 per session on Opus 5.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.
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…
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…
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-content-officer
Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit…
incident-management
Runs an operational incident from detection to closed action — declaring it and naming a commander, separating the people restoring service from the people communicating, keeping a timeline as it happens, deciding when it is over, and running a review that produces a small number of changes someone actually completes.…