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 JasonColapietro/suede-creator-skills --skill suede-product-marketinggit clone --depth 1 https://github.com/JasonColapietro/suede-creator-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/jasoncolapietro/suede-creator-skills/suede-product-marketing)<a href="https://agentmods.dev/skills/jasoncolapietro/suede-creator-skills/suede-product-marketing"><img src="https://agentmods.dev/badge/skills/jasoncolapietro/suede-creator-skills/suede-product-marketing/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/jasoncolapietro/suede-creator-skills/suede-product-marketing"><img src="https://agentmods.dev/badge/skills/jasoncolapietro/suede-creator-skills/suede-product-marketing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.02774 |
| Opus 5 | $0.00041 | $0.01387 |
| Sonnet 5 | $0.00016 | $0.00555 |
| Haiku 4.5 | $0.00008 | $0.00277 |
Grade A, and why
suede-product-marketing 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 9d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Suede Product Marketing Context
Suede Product Marketing maintains the shared evidence layer for audience, positioning, objections, customer language, and proof. The Suede growth suite reads this context so each downstream skill starts from the same verified product story.
The document is stored at .agents/product-marketing.md.
Workflow
Step 1: Check for Existing Context
First, check if .agents/product-marketing.md already exists. Also check .claude/product-marketing.md and the legacy filename product-marketing-context.md (in either .agents/ or .claude/) for older setups — if found anywhere other than .agents/product-marketing.md, offer to move it to the canonical location.
If it exists:
- Read it and summarize what's captured — note its current Document version and the last few Changelog entries so the user sees where the doc stands and what's changed recently
- Ask which sections they want to update
- Only gather info for those sections
- On any substantive save, bump the version and add a changelog entry (see Step 4). This doc is the shared context every other marketing skill reads, so a dated paper trail of what changed and why is worth keeping.
If it doesn't exist, offer two options:
-
Auto-draft from codebase (recommended): You'll study the repo—README, landing pages, marketing copy, package.json, etc.—and draft a V1 of the context document. The user then reviews, corrects, and fills gaps. This is faster than starting from scratch.
-
Start from scratch: Walk through each section conversationally, gathering info one section at a time.
Most users prefer option 1. After presenting the draft, ask: "What needs correcting? What's missing?"
Step 2: Gather Information
If auto-drafting:
- Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
- Draft only what the sources actually say. Every auto-drafted field carries its source in the form
[src: path/to/file.md]— the file the claim came from. A field with no source is not drafted: leave it empty and mark it[unverified]. - Never source a field from inference. If the README implies a differentiator without stating it, if a competitor is guessed from the category, or if a testimonial-shaped sentence in marketing copy has no attributed customer, that field is
[unverified]— not a draft with a hedge. Differentiation, Competitive Landscape, Proof Points, and Customer Language are where this rule earns its keep; a fabricated entry there propagates to every skill that reads this doc. - Present the draft and say plainly how many fields are sourced versus
[unverified], then ask what needs correcting or is missing - Iterate until the user is satisfied. A field the user confirms in conversation is sourced as
[src: user]
What ships with it
3 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.
- 9d ago First seen · 282 lines · 81 tokens per session scan A 80b60257ff98
suede-product-marketing is a skill published in the GitHub repository JasonColapietro/suede-creator-skills (135 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 2,774 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
pdf-text-replace
Replace text in fillable PDF forms by updating form field values. This skill should be used when users need to update names, addresses, dates, or other text in PDF form fields.
design-export-repair
Fixes broken decks/PDFs exported from Claude's "Design" feature (or similar AI deck generators) — cut-off or clipped text, wrong/substituted fonts, and corrupted .pptx package structure that shows up only once you export to PDF, not while looking at it in the app. Use this skill whenever the user uploads a zip, .pptx…
google-apps-script
Build Google Apps Script automation for Sheets and Workspace. Custom menus, triggers (onEdit / time-driven / form submit), dialogs, sidebars, email batches, PDF export, external API. Use whenever the user wants to automate a Google Sheet, build a Sheets menu / sidebar / dialog, hit a Sheets row from email or a…
financial-document-parser
Extract and analyze data from invoices, receipts, bank statements, and financial documents. Categorize expenses, track recurring charges, and generate expense reports. Use when user provides financial PDFs or images.
csv-excel-merger
Merge multiple CSV/Excel files with intelligent column matching, data deduplication, and conflict resolution. Handles different schemas, formats, and combines data sources. Use when users need to merge spreadsheets, combine data exports, or consolidate multiple files into one.
brand-consistency-checker
Scan documents and slides for off-brand colors, fonts, and logos. Validate against brand guidelines and suggest corrections.