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-features-listgit 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-features-list)<a href="https://agentmods.dev/skills/ljucask/pureinn-product-development/pm-features-list"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-features-list/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-features-list"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-features-list.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.00098 | $0.08875 |
| Opus 5.5 | $0.00039 | $0.03550 |
| Sonnet 5.5 | $0.00020 | $0.01775 |
| Haiku 4.5 | $0.00010 | $0.00887 |
Grade A, and why
pm-features-list 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 — 746 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM - Features List
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.- Review required: the artifact contains commitments - after drafting, require the user's review before finalizing; do not close decisions autonomously.
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
Phase 5 / Step 1-3. Takes the product scope from PRD Business Capabilities and produces:
- FDD Feature List (
features/feature_list.md) - Live Register 4. All features in FDD format ([Action] [Result] [Object]), organized in 3-level hierarchy: Domain -> Feature Set -> Feature. With actor, priority, dependencies, MVP flag, and stripe assignment. - Dependency Map - which features block which, critical path, parallelizable tracks
- KANO Analysis - must-be / performance / delighter / indifferent classification per feature
- Value vs. Complexity Matrix - Quick Win / Big Bet / Fill-in / Time Waster scoring per feature
- Stub Feature Cards - one per feature, created automatically in
/features/cards/FEAT-[DOMAIN]-[NUMBER].mdwith status1_Backlog
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 · +20 lines 2184b6e82747
- 1mo ago Changed · +9 lines c14567e1fbbe
- 1mo ago First seen · 717 lines · 98 tokens per session scan A fbc82a84110d
pm-features-list is a skill published in the GitHub repository ljucask/pureinn-product-development (2 stars, last pushed 19d ago), licensed MIT. It adds 98 tokens to every session and 8,875 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
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.
backend-development
A set of instructions for building server-side code such as APIs and database-backed applications. It uses API contracts, data models, the chosen technology stack, and tests as the project’s reference points.
decision-gate
A decision checkpoint for software-project workflows. After each phase produces its files, it asks the user to accept the result, request a change, add information, or regenerate it before the next phase begins.
frontend-development
A set of instructions for building the user-facing part of a web application, such as its pages, controls, and interactions. It applies to single-page applications and follows the project’s API, product, technology, and design documents.
relay
A Chinese-language procedure for handing an unfinished task from one AI session to another without losing its context.
validation-loop
A development routine that checks each important file immediately after it is changed by running the project’s build, lint, type-check, or test commands.