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-stripegit 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-stripe)<a href="https://agentmods.dev/skills/ljucask/pureinn-product-development/pm-stripe"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-stripe/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-stripe"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-stripe.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.00078 | $0.16628 |
| Opus 5 | $0.00039 | $0.08314 |
| Sonnet 5 | $0.00016 | $0.03326 |
| Haiku 4.5 | $0.00008 | $0.01663 |
Grade B, and why
pm-stripe scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -u "$AIKIDO_CLIENT_ID:$AIKIDO_CLIENT_SECRET" -d grant_type=client_credentials {base_url}/oauth/token Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -u "$AIKIDO_CLIENT_ID:$AIKIDO_CLIENT_SECRET" -d grant_type=client_credentials {base_url}/oauth/token How it starts
The opening of the file, as written. The whole thing — 800 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM - Delivery Stripe
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
Run this every time you sit down to work on Phase 6-7. It is not a one-time setup skill - it is your session start point.
pm-stripe reads the current state of all active stripes, detects where each active feature is in the lifecycle, and tells you exactly what to do next. It routes you to the right skill at the right moment.
Division of responsibility:
features/feature_list.md- source of truth for feature inventory, priority, stripe assignment, dependency order/features/cards/FEAT-*.md- source of truth for feature status and spec content- This skill - session orchestrator: detects state, routes to right skill, tracks transitions, runs Impact Analysis
Full feature lifecycle:
| Status | Meaning | Who sets it |
|---|---|---|
1_Backlog |
In queue, design not started | pm-features-list (auto) |
2_Spec_Done |
JIT spec complete (Sections 1-3 written), awaiting design inspection | pm-feature-design |
2b_In_Design |
(optional - frontend features only) UI / Figma design being produced | pm-feature-design / designer |
3_Ready_to_Build |
Design inspection approved, ready to enter build | pm-stripe (human confirms) |
4_In_Build |
Build skills actively working on this feature | pm-stripe |
5_In_Review |
Build complete, code review in progress | pm-stripe |
6_Shipped |
Complete - code reviewed, Section 4 filled, Feature Card immutable | pm-stripe |
Two independent axes - never conflate them (critical for Rebuild). status and build order are two separate things:
status= code reality. What the code actually is right now (nothing built / partially built / shipped). Owned by whoever observed the code:pm-stripein greenfield (it moves the status forward),pm-reverse-extract/pm-reconcilein a Rebuild (they set it from the codebase).- Plan order (
plan_order/wave+active_feature) = the schedule. What we work on next and who is on which lane. Owned by the Delivery Plan computation + the human picking up work.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 800 lines · 78 tokens per session scan B 2e06e17a9836
pm-stripe is a skill published in the GitHub repository ljucask/pureinn-product-development (2 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 16,628 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). 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…