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 sungurerdim/dev-skills --skill ds-productizegit clone --depth 1 https://github.com/sungurerdim/dev-skillsWrote 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/sungurerdim/dev-skills/ds-productize)<a href="https://agentmods.dev/skills/sungurerdim/dev-skills/ds-productize"><img src="https://agentmods.dev/badge/skills/sungurerdim/dev-skills/ds-productize.svg" alt="Measured on agentmods" 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.00045 | $0.04400 |
| Opus 5 | $0.00023 | $0.02200 |
| Sonnet 5 | $0.00009 | $0.00880 |
| Haiku 4.5 | $0.00005 | $0.00440 |
Grade A, and why
ds-productize 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 5d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ds-productize
Projects reach technical ship-readiness with zero revenue readiness: no monetization model chosen, paid features unenforced, pricing invented in the release week, and no funnel instrumentation to learn from. Skill audits the business layer with the same file:line rigor the rest of the suite applies to code.
Productize — monetization, pricing/packaging, and go-to-market readiness audit + productization plan.
Completion Evidence — applies to every phase: Report
done/OKonly with the machine-checkable evidence the gates name — the exact command run and its observed output (orfile:linediff). Missing evidence → reportINCOMPLETEplus what is missing. Self-assessment is never evidence. (This band repeats at file end by design — both copies are normative.)
Triggers
- User runs
/ds-productize, or asks to turn a project into a paid product/SaaS, audit monetization/paywall/billing readiness, design pricing tiers or packaging, or check go-to-market readiness — see the table below for concrete phrases
Triggers — INVOKE / DON'T INVOKE
| INVOKE | DON'T INVOKE |
|---|---|
| "make this a paid SaaS", "monetization audit" | "optimize store listing / ASO" (→ ds-launch) |
| "design pricing tiers / packaging" | "full GDPR/KVKK privacy audit" (→ ds-compliance --privacy) |
| "is my paywall/billing production-ready" | "review billing API code quality" (→ ds-backend --audit) |
| "go-to-market readiness check" | "research competitors' architecture" (→ ds-benchmark) |
| "why does nobody convert to paid" | "optimize a conversion metric via experiments" (→ ds-tune) |
Contract
Dimensions: A1 (GTM), A2, A3 (funnel), A11 (GTM signal)
- Covers three scopes: monetization (model + billing/entitlement integrity), pricing (metric + tiers + packaging + channels + unit economics), gtm (positioning + funnel baseline, including funnel-analytics instrumentation — ops telemetry delegated to ds-deploy).
- Audits and plans — generates findings and
ds/productize/plan.md; payment-provider integration code itself is implemented by the user or ds-backend. - Only recommends established patterns with published benchmarks — no speculative growth hacks.
- Minimal liability + maximum privacy: recommends Merchant-of-Record or managed billing over hand-rolled payment handling; funnel metrics are privacy-first (no PII in events, consent-gated where required).
- Standalone. Uses blueprint profile or
ds/audit/findings.mdwhen available; own analysis when absent. - State-exempt: audit + plan are regenerable from source; the plan file and git are the durable record.
- Full accounting enforced: every finding and planned check ends in an explicit disposition (fixed / skipped + reason / only you can do); summary totals balance.
- Pre-existing / out-of-scope errors detected during work are NOT skipped — fixed inline or escalated with concrete blocker.
What ships with it
5 files 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.
- 5d ago Changed · +2 lines 462237d407bd
- 8d ago First seen · 194 lines · 45 tokens per session scan A 3731f902ffab
ds-productize is a skill published in the GitHub repository sungurerdim/dev-skills (1 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 4,400 once invoked, about $0.0002 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
memstack-business-financial-model
Use this skill when the user says 'financial model', 'projections', 'revenue forecast', 'unit economics', 'break-even', 'cash flow', or mentions MRR, churn, CAC, LTV, or runway. Builds monthly projections with scenario modeling. Do NOT use for pricing strategy or invoice generation.
memstack-business-invoice-generator
Use this skill when the user says 'invoice', 'generate invoice', 'create invoice', 'bill client', 'line items', 'payment terms', or needs professional invoices with tax calculations and payment instructions. Do NOT use for contracts or financial projections.
memstack-business-freelancer-toolkit
Use when the user says 'track my time', 'freelancer invoice', 'billable hours', 'time tracking', 'freelance finances', 'client billing', 'project hours', or needs invoicing, time tracking, or analytics patterns for freelance work. Do NOT use for general invoice templates or proposal writing.
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
ring:using-lib-streaming
Using lib-streaming, Lerian's producer-only event publication library (Kafka/SQS/RabbitMQ/EventBridge), in two modes. Sweep Mode detects DIY publishers (franz-go, sarama, amqp091, watermill, raw AWS SDK) and re-rolled manifests/breakers. Reference Mode catalogs the Builder/Emitter/Catalog facade. Companion to…
ring:using-lib-systemplane
Using lib-systemplane, the hot-reload runtime-config plane (Postgres LISTEN/NOTIFY or MongoDB change streams), in two modes. Sweep Mode detects DIY config reload (SIGHUP, fsnotify, viper, pgx LISTEN), manual tenant-scoping, hand-built admin CRUD, and v4 residue. Reference Mode catalogs client lifecycle and…