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-reconcilegit 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-reconcile)<a href="https://agentmods.dev/skills/ljucask/pureinn-product-development/pm-reconcile"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-reconcile/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-reconcile"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-reconcile.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.00262 | $0.08802 |
| Opus 5 | $0.00131 | $0.04401 |
| Sonnet 5 | $0.00052 | $0.01760 |
| Haiku 4.5 | $0.00026 | $0.00880 |
Grade A, and why
pm-reconcile 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 11d 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 — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM - Reconcile (Rebuild from Existing Product)
Agent mode (--agent)
This skill's value is the live dialogue - --agent is not supported. If invoked with --agent, warn once ("this skill needs interactive back-and-forth; agent mode would hollow it out") and proceed interactively.
What this skill does
Takes an existing product - working code plus a pile of legacy, possibly inconsistent documentation - and rebuilds a clean Pureinn structure that matches reality. It runs in two phases:
- PLAN - inspect the old-docs folder and the codebase surface, detect which areas exist, map each to its target Pureinn artifact, and define the order. Output:
reconciliation_plan.md. - EXECUTE per area -
/pm-reconcile [area]reconciles one layer at a time in the planned order, asking about real business-logic conflicts, appending to a living Reconciliation Report, and rebuilding that layer's register.
Reconciliation can span multiple sessions. Progress is held in state.json and shown by /pm-reconcile-status.
This is the Rebuild playbook referenced in the /pureinn orchestrator. Run it when a product was built outside Pureinn, legacy docs disagree with the code and each other, and the (often new) team needs one trustworthy source of truth.
Invocation modes
| Command | Mode | Does |
|---|---|---|
/pm-reconcile |
Plan / route | No plan yet → build the Reconciliation Plan. Plan exists → short status + point to the next area (full dashboard via /pm-reconcile-status). |
/pm-reconcile plan |
Plan (force) | Re-inspect and rebuild the plan. |
/pm-reconcile domain |
Execute | Reconcile entities + attributes + enums + state machine structure → entities.md (Register 1) + glossary aliases. Offers the cross-domain ERD → domain-model.md. |
/pm-reconcile rules |
Execute | Reconcile business rules + decision models + transition guard conditions → business_rules.md + decision_models.md (Registers 2-3). |
/pm-reconcile features |
Execute | Reconcile feature inventory → feature_list.md + stub Feature Cards Section 1 (Register 4). |
/pm-reconcile [other] |
Execute | Any extra area the plan defined (e.g. events, integrations). |
/pm-reconcile open-questions |
Execute | Route to /pm-open-questions migrate - scan every artifact + Notion for scattered OQ-*/DIV-*/BLK-*/TBD items and consolidate them into domain/open_questions.md (Register 5). Run any time; typically after the other areas surface divergences and blockers. |
/pm-reconcile verify [area] |
Verify + incorporate | Re-read the source one more time, prove every unit landed in the registers, incorporate the gaps it finds (not just report them), and rule on disposal readiness. The source-disposal gate. Default = all areas; scope with verify domain | rules | features. |
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.
- 11d ago First seen · 444 lines · 262 tokens per session scan A 005749f8c90b
pm-reconcile is a skill published in the GitHub repository ljucask/pureinn-product-development (2 stars, last pushed yesterday), licensed MIT. It adds 262 tokens to every session and 8,802 once invoked, about $0.0013 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…