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 license-keysgit 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/license-keys)<a href="https://agentmods.dev/skills/dodopayments/dodo-agent-plugin/license-keys"><img src="https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/license-keys.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.00026 | $0.04408 |
| Opus 5 | $0.00013 | $0.02204 |
| Sonnet 5 | $0.00005 | $0.00882 |
| Haiku 4.5 | $0.00003 | $0.00441 |
Grade A, and why
license-keys 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 7d 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.
This is a copy
100% identical to license-keys — 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 — 717 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dodo Payments License Keys
License keys authorize access to your digital products. Use them for software licensing, per-seat controls, and gating premium features.
When to use this skill
- Implementing end-user license activation and validation flows
- Building merchant dashboards to manage customer license keys
- Handling license expiry, activation limits, and subscription-linked revocation
- Integrating license checks into desktop apps, CLIs, or web services
- Reacting to license lifecycle webhooks
Core concepts
License Key Entitlements deliver keys when a product is purchased. The entitlement config supplies activation limits, optional duration, and fulfillment mode (auto or manual).
Three distinct resources:
-
client.licenses.*— end-user activation flow (public, no API key required)activate()— activate a key on a devicevalidate()— check if a key is validdeactivate()— free an activation slot
-
client.licenseKeys.*— merchant-side key management (requires API key)list(),retrieve(),create(),update()— manage keys for your customers
-
client.licenseKeyInstances.*— per-device activation instances (requires API key)list(),retrieve(),update()— track active devices per key
Activation limits: blank/null means unlimited; otherwise it's the maximum concurrent activations. Attempting to activate beyond the limit returns 422.
Expiry semantics:
- One-time-payment keys honor the entitlement duration.
- Subscription-issued keys have no independent expiry; validity follows subscription state. On hold disables them temporarily. An immediate cancellation disables them permanently, but when
cancel_at_next_billing_dateis set, keep them active until the subscription reaches the end of its term. - Imported keys use nullable
expires_at; null means perpetual.
End-User Activation Flow
Activate a license key
import DodoPayments from 'dodopayments';
// No API key needed for public endpoints
const client = new DodoPayments();
async function activateLicense(licenseKey: string, deviceName: string) {
try {
const response = await client.licenses.activate({
license_key: licenseKey,
name: deviceName, // e.g., "John's MacBook Pro"
});
return {
success: true,
instanceId: response.id,
customerId: response.customer.customer_id,
productId: response.product.product_id,
};
} catch (error: any) {
if (error.status === 422) {
return { success: false, error: 'Activation limit reached' };
}
return { success: false, error: error.message || 'Activation failed' };
}
}
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.
- 7d ago First seen · 717 lines · 26 tokens per session scan A c3d320bdb692
license-keys is a skill published in the GitHub repository dodopayments/dodo-agent-plugin (6 stars, last pushed 7d ago), licensed MIT. It adds 26 tokens to every session and 4,408 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to license-keys, 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.