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-reverse-extractgit 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-reverse-extract)<a href="https://agentmods.dev/skills/ljucask/pureinn-product-development/pm-reverse-extract"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-reverse-extract/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-reverse-extract"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-reverse-extract.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.00143 | $0.05650 |
| Opus 5 | $0.00072 | $0.02825 |
| Sonnet 5 | $0.00029 | $0.01130 |
| Haiku 4.5 | $0.00014 | $0.00565 |
Grade A, and why
pm-reverse-extract 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.
How it starts
The opening of the file, as written. The whole thing — 465 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM - Reverse Extract (Existing Product Sync)
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
Extracts the full feature inventory from an existing product and formalizes it into the FDD+SDD framework.
Run order for migration path:
/pm-entity-registry- extracts entities and state machines →domain/entities.md/pm-business-rules-library- extracts business rules →domain/business_rules.md+domain/decision_models.md/pm-reverse-extract(this skill) - extracts feature inventory →features/feature_list.md+ stub Feature Cards
Produces:
feature_list.md(Live Register 4) - full feature inventory in FDD format with FEAT-[DOMAIN]-NNN IDs- Stub Feature Cards in
features/cards/- one per feature, status:1_Backlog - Delivery Stripe assignment - which features go into which domain stripe
- Notion push - Feature hierarchy pushed to Product Features database
Claude reads directly: codebase, existing docs, API specs, route files, controller files. This skill structures what Claude already knows - it does not hallucinate features.
Can be re-run at any point to re-sync Notion after significant state changes.
Reconciled mode (when run by pm-reconcile): If reconcile/reconciliation_report.md exists, it is the authoritative input. Derive features from the reconciled code reality, map the old feature names as aliases, include code-only features from the report, and do NOT create cards for doc-only / not-implemented items (those are backlog). Do not re-question what the report already settled.
What this skill does NOT do
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 · 465 lines · 143 tokens per session scan A 3a5826e07322
pm-reverse-extract is a skill published in the GitHub repository ljucask/pureinn-product-development (2 stars, last pushed 29d ago), licensed MIT. It adds 143 tokens to every session and 5,650 once invoked, about $0.0007 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.
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…
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-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…