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 dodopayments/dodo-agent-plugin --skill product-catalog-managementgit clone --depth 1 https://github.com/dodopayments/dodo-agent-pluginWrote 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/dodopayments/dodo-agent-plugin/product-catalog-management)<a href="https://agentmods.dev/skills/dodopayments/dodo-agent-plugin/product-catalog-management"><img src="https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/product-catalog-management/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/dodopayments/dodo-agent-plugin/product-catalog-management"><img src="https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/product-catalog-management.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.00026 | $0.02267 |
| Opus 5 | $0.00013 | $0.01133 |
| Sonnet 5 | $0.00005 | $0.00453 |
| Haiku 4.5 | $0.00003 | $0.00227 |
Grade A, and why
product-catalog-management scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(uploadUrl.url, { This is a copy
100% identical to product-catalog-management — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Catalog Management
This skill covers the full product lifecycle: creating products with pricing models, managing add-ons and collections, uploading product images, and delivering digital files to customers.
When to use this skill
- You need to create or update products with one-time, recurring, or usage-based pricing.
- You're building a product collection or storefront.
- You need to upload product images or deliver digital files to customers.
- You're managing add-ons or product variants.
- You need to understand why a product update failed or why pricing can't be changed.
Core concepts
Product model: Every product has exactly one pricing model selected at creation. The three models are:
one_time_price: charge once per purchase.recurring_price: charge on a configurable payment frequency and subscription period.usage_based_price: charge per unit consumed (seeusage-based-billingskill for meter setup).
Pricing is nested inside the product object. There is no separate top-level Price resource.
Pricing structure: Each price object contains:
type: one of the three models above.currency: ISO 4217 code (e.g.,USD,AED,INR).price: amount in the smallest currency unit (cents for USD).discount: optional discount amount in the same unit.
Tax category: Required at product creation. Dodo uses this to calculate and collect sales tax. Supported values are digital_products, saas, e_book, and edtech.
Lifecycle: Products support list, retrieve, update, and archive/unarchive. There is no delete endpoint. Archived products remain in your history but don't appear in new checkouts.
Images: Presigned upload URLs expire after 60 seconds. Download the URL immediately after requesting it.
Digital delivery: Entitlements grant customers access to files. Download URLs expire after roughly 15 minutes.
Creating a product
All products require a name, a pricing model, and a tax category.
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.
- 10d ago First seen · 312 lines · 26 tokens per session scan A b41184dfbc9e
product-catalog-management is a skill published in the GitHub repository dodopayments/dodo-agent-plugin (6 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 2,267 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to product-catalog-management, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
opencode-ensemble
Use when coordinating multiple coding agents, delegating independent software work, managing OpenCode Ensemble teams, choosing teammate roles or models, reviewing teammate output, or deciding whether parallel execution is appropriate.
ahk-consultant
Get technical advice or review on an approach, idea, or change. References available skills for best practices. No tasks created, no harness tracking.
ce:review
Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. Use when reviewing code changes before creating a PR.
ce:compound-refresh
Refresh stale or drifting learnings and pattern docs in docs/solutions/ by reviewing, updating, consolidating, replacing, or deleting them against the current codebase. Use after refactors, migrations, dependency upgrades, or when a retrieved learning feels outdated or wrong. Also use when reviewing docs/solutions/…
ce:compound
Document a recently solved problem to compound your team's knowledge.
ce:work
Execute work efficiently while maintaining quality and finishing features.