license-keys

license-keys is a skill for Claude Code from dodopayments/dodo-agent-plugin. It costs 26 tokens per session (4,408 once invoked), scanned A, a copy of license-keys, MIT.

A guide to license keys that control access to software or digital products. It covers activating and checking keys, limiting device activations, and revoking access when needed.

In plain words
What is it for?
Use it to add licensing to desktop apps, command-line tools, web services, or merchant dashboards, including key activation, validation, deactivation, expiry, and lifecycle events.
Why use it?
It provides the rules for connecting a purchase to software access without handling activation, expiry, and subscription changes ad hoc.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the dodopayments plugin — 17 skills, 2 MCP servers shipped together

Good fit Use it to add licensing to desktop apps, command-line tools, web services, or merchant dashboards, including key activation, validation, deactivation, expiry, and lifecycle events.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dodopayments/dodo-agent-plugin/license-keys
Install

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.

Any agent
npx skills add dodopayments/dodo-agent-plugin --skill license-keys
Clone the repo
git clone --depth 1 https://github.com/dodopayments/dodo-agent-plugin

Made for: Claude Code.

Or install dodopayments, the plugin that ships this one along with the rest of its 17 skills, 2 MCP servers.

Wrote 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.

agentmods badge for license-keys

README.md
[![agentmods](https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/license-keys.svg)](https://agentmods.dev/skills/dodopayments/dodo-agent-plugin/license-keys)
Your own site
<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>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,408 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 7d ago against content hash c3d320bdb692, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

Origin

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.

plugins/dodopayments/skills/license-keys/SKILL.md · 717 lines

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:

  1. client.licenses.* — end-user activation flow (public, no API key required)

    • activate() — activate a key on a device
    • validate() — check if a key is valid
    • deactivate() — free an activation slot
  2. client.licenseKeys.* — merchant-side key management (requires API key)

    • list(), retrieve(), create(), update() — manage keys for your customers
  3. 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_date is 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' };
  }
}

Read the full file on GitHub · 717 lines

Changes

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.

  1. 7d ago First seen · 717 lines · 26 tokens per session scan A c3d320bdb692

Subscribe to this mod's changes

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.