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 dansasser/claude-code-marketplace --skill product-promogit clone --depth 1 https://github.com/dansasser/claude-code-marketplaceWrote 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/dansasser/claude-code-marketplace/product-promo)<a href="https://agentmods.dev/skills/dansasser/claude-code-marketplace/product-promo"><img src="https://agentmods.dev/badge/skills/dansasser/claude-code-marketplace/product-promo/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/dansasser/claude-code-marketplace/product-promo"><img src="https://agentmods.dev/badge/skills/dansasser/claude-code-marketplace/product-promo.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.00033 | $0.00405 |
| Opus 5 | $0.00016 | $0.00202 |
| Sonnet 5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
product-promo 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 12d 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.
What it actually says
Use the Remotion best practices skill (SKILL.md at the plugin root). Follow its scene planning algorithm for all production steps.
Product Promo
Input
$ARGUMENTS
Questionnaire
If not answered by the input, ask:
- What product/service? — URL to research
- What's the hook? — The pain point or attention grabber. Or should I figure it out from the page?
- CTA? — What should the viewer do? (default: visit the URL)
Script
Research the URL. Extract: what it is, who it's for, key features, pricing, differentiators, governance/trust signals, and CTA. Write a 5-scene script. Present for approval before building. Each scene needs:
- One-line headline (on screen)
- Voiceover script (natural, conversational, punchy)
- Visual description
Scene Structure
- Scene 1: Hook — pain point, grab attention in 2 seconds
- Scene 2: The solution — what it is, key value prop, pricing if applicable
- Scene 3: Capabilities — what it does, features with b-roll background
- Scene 4: Trust — governance, security, differentiators with b-roll background
- Scene 5: CTA — what to do next, URL on screen, logo
B-Roll Prompts
Generate b-roll prompts based on the product/service context:
- Scene 3: match the product's use case (office, tech, lifestyle, etc.)
- Scene 4: match the trust angle (security, data, professional, abstract)
- Scene 5: match the brand identity
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.
- 12d ago First seen · 39 lines · 33 tokens per session scan A 859518fb55f2
product-promo is a skill published in the GitHub repository dansasser/claude-code-marketplace (9 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 405 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…