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-process-flowsgit 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-process-flows)<a href="https://agentmods.dev/skills/ljucask/pureinn-product-development/pm-process-flows"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-process-flows/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-process-flows"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-process-flows.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.00120 | $0.03099 |
| Opus 5 | $0.00060 | $0.01550 |
| Sonnet 5 | $0.00024 | $0.00620 |
| Haiku 4.5 | $0.00012 | $0.00310 |
Grade A, and why
pm-process-flows 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 8d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM - Process Flows (User Types + Process Maps + User Flows)
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
Two connected outputs that bridge the domain model into design:
- System user types - the actors/roles in the system (e.g. Admin, Courier, Dispatcher, Customer, System). Identified adaptively.
- Flows - two views built on those user types:
- 2A. Process map per domain / process area - the end-to-end business process, for dev + design understanding.
- 2B. User flows per user type, connected to screens - how each user moves through the processes E2E, with screen touchpoints and UI behaviour, so a designer can complete the screen design from the user's perspective.
This sits between the domain registers and per-feature design. pm-feature-design's per-feature UX context (Section 3b) is atomic; this gives the E2E big picture across a module that the per-feature view then refines.
Lean by design (low maintenance): process maps and flows reference entity states and attributes by name - they do NOT restate state machines or attribute lists (those live in entities.md). If a state changes, you change it once in the register, not across a dozen diagrams. This skill is a business + UX view, not a second copy of the domain.
Adaptive (per the Adaptive-execution standard in CLAUDE.md): runs with whatever exists (personas? domain? features?), is re-runnable per module, and offers rather than imposes.
Produces:
process-flows/user_types.md- the system actor catalogueprocess-flows/[domain]_process_map.md- the 2A business process map per domainprocess-flows/[domain]_user_flows.md- the 2B per-user screen-connected flows
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.
- 8d ago First seen · 267 lines · 120 tokens per session scan A 8b9375c31d97
pm-process-flows is a skill published in the GitHub repository ljucask/pureinn-product-development (2 stars, last pushed 29d ago), licensed MIT. It adds 120 tokens to every session and 3,099 once invoked, about $0.0006 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.
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.
huashu-keynote-black
OpenDesign's all-hands: the year in review, the three priorities, and what every team owns next quarter. Built as a decision-grade corporate strategy deck for whole company.
acid-blue-business
A visual presentation style for modern business topics, using electric blue with black, white, and grey, directional layouts, and clear spacing. It is intended for business content rather than traditional data dashboards.
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…