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 agentmods add skills/cwinvestments/memstack/product-descriptionnpx skills add cwinvestments/memstack --skill product-descriptiongit clone --depth 1 https://github.com/cwinvestments/memstackWrote 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/cwinvestments/memstack/product-description)<a href="https://agentmods.dev/skills/cwinvestments/memstack/product-description"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/product-description.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 | $0.00065 | $0.02480 |
| Opus 5 | $0.00032 | $0.01240 |
| Sonnet 5 | $0.00013 | $0.00496 |
| Haiku 4.5 | $0.00006 | $0.00248 |
Grade A, and why
memstack-content-product-description 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 today.
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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Description: Writing product copy...
Creates conversion-optimized product descriptions with feature-to-benefit conversion, sensory language, SEO keywords, A/B variants, and platform-specific formats for Amazon, Shopify, and Etsy.
Activation
When this skill activates, output:
Product Description: Writing product copy...
Then execute the protocol below.
Context Guard
| Context | Status |
|---|---|
| User says "product description", "product listing", "product copy" | ACTIVE |
| User says "Amazon listing", "Shopify listing", "e-commerce copy" | ACTIVE |
| User wants to write or improve copy for a product listing | ACTIVE |
| User wants to set pricing | DORMANT: use Pricing Strategy |
| User wants a full sales funnel | DORMANT: use Sales Funnel |
Common Mistakes
| Mistake | Why It's Wrong |
|---|---|
| "List features, not benefits" | "500mAh battery" means nothing. "Lasts 12 hours so you never run out mid-day" sells. |
| "Generic descriptions" | "High quality product" could describe anything. Be specific about WHAT makes it quality. |
| "Ignore the platform" | Amazon, Shopify, and Etsy have different algorithms, formats, and buyer expectations. |
| "No keywords" | E-commerce search is keyword-driven. No keywords = invisible in search results. |
| "One version only" | A/B testing descriptions is easy and can improve conversion 10-30%. Write variants. |
Protocol
Step 1: Gather Product Details
If the user hasn't provided details, ask:
- Product: what is it? (name, category, physical/digital)
- Features: what are its key specs and features? (list 5-10)
- Audience: who buys this? (demographics, use case, pain point)
- Platform: where is it listed? (Amazon, Shopify, Etsy, other)
- Price point: what does it cost? (affects copy tone and positioning)
- Competitors: what are the top 3 alternatives? (for differentiation)
Step 2: Feature-to-Benefit Conversion
Transform every feature into a customer benefit:
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.
- today Changed 7723dc3da6d5
- 4d ago First seen · 284 lines · 65 tokens per session scan A 658782a1e137
memstack-content-product-description is a skill published in the GitHub repository cwinvestments/memstack (419 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 2,480 once invoked, about $0.0003 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-30.
Other skills, from other repositories
plan-ceo-review
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when…
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Use for an explicit /ship invocation or when the user requests the full ship, release, or deploy workflow. For an ordinary commit, push, or pull-request publishing request, use the built-in…
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…
retro
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively…