unlayer-integration

unlayer-integration is a skill for Claude Code, Codex from unlayer/unlayer-skills. It costs 69 tokens per session (2,532 once invoked), scanned A, original, MIT.

A guide for embedding Unlayer's email, page, popup, and document builders in React, Vue, Angular, or plain JavaScript applications. It explains the package and editor access pattern for each environment.

In plain words
What is it for?
Use it to add Unlayer builders to a web app, configure them, access their APIs, and work with more than one editor.
Why use it?
It removes guesswork when installing the correct wrapper and accessing the embedded editor from application code. It also covers using multiple editor instances and checking package versions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to add Unlayer builders to a web app, configure them…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/unlayer/unlayer-skills/unlayer-integration
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 unlayer/unlayer-skills --skill unlayer-integration
Clone the repo
git clone --depth 1 https://github.com/unlayer/unlayer-skills

Made for: Claude Code, Codex.

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 unlayer-integration

README.md
[![agentmods](https://agentmods.dev/badge/skills/unlayer/unlayer-skills/unlayer-integration.svg)](https://agentmods.dev/skills/unlayer/unlayer-skills/unlayer-integration)
Your own site
<a href="https://agentmods.dev/skills/unlayer/unlayer-skills/unlayer-integration"><img src="https://agentmods.dev/badge/skills/unlayer/unlayer-skills/unlayer-integration.svg" alt="Measured on agentmods" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,532 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 original No closer match found 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.00069 $0.02532
Opus 5 $0.00034 $0.01266
Sonnet 5 $0.00014 $0.00506
Haiku 4.5 $0.00007 $0.00253

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

Security

Grade A, and why

unlayer-integration 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.

unlayer-integration/SKILL.md · 354 lines

How it starts

The opening of the file, as written. The whole thing — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Integrate Unlayer Editor

Overview

Unlayer provides official wrappers for React, Vue, and Angular, plus a plain JavaScript embed. All wrappers share the same underlying API — only the editor access pattern differs.

This skill covers the email, page, popup, and document builders. For the standalone Image Editor or @unlayer/react-image-editor, use unlayer-image-editor.

Which Framework?

Framework Package Install Editor Access
React react-email-editor npm i react-email-editor useRef<EditorRef>ref.current?.editor
Vue vue-email-editor npm i vue-email-editor this.$refs.emailEditor.editor
Angular angular-email-editor npm i angular-email-editor @ViewChildthis.emailEditor.editor
Plain JS CDN script tag <script> embed Global unlayer object

⚠️ Before installing any Unlayer package, verify the version exists on npm:

npm view react-email-editor version   # check latest published version

Never pin a version number you haven't verified. Use npm install <package> --save without a version to get the latest, or run npm view <package> versions --json to see all available versions.


React (Complete Working Example)

npm install react-email-editor --save
import React, { useRef, useState } from 'react';
import EmailEditor, { EditorRef, EmailEditorProps } from 'react-email-editor';

const EmailBuilder = () => {
  const emailEditorRef = useRef<EditorRef>(null);
  const [saving, setSaving] = useState(false);

  // Save design JSON + export HTML to your backend
  const handleSave = () => {
    const unlayer = emailEditorRef.current?.editor;
    if (!unlayer) return;

    setSaving(true);
    unlayer.exportHtml(async (data) => {
      try {
        const response = await fetch('/api/templates', {
          method: 'POST',
          headers: { 'Content-Type': 'application/json' },
          body: JSON.stringify({
            design: data.design,  // Save this — needed to edit later
            html: data.html,      // The rendered HTML output
          }),
        });
        if (!response.ok) throw new Error('Save failed');
        console.log('Saved successfully');
      } catch (err) {
        console.error('Save error:', err);
      } finally {
        setSaving(false);
      }
    });
  };

  // Load a saved design when editor is ready
  const onReady: EmailEditorProps['onReady'] = async (unlayer) => {
    try {
      const response = await fetch('/api/templates/123');
      if (response.ok) {
        const saved = await response.json();
        unlayer.loadDesign(saved.design); // Pass the saved design JSON
      }
    } catch (err) {
      console.log('No saved design, starting blank');
    }
  };

  return (
    <div>
      <button onClick={handleSave} disabled={saving}>
        {saving ? 'Saving...' : 'Save'}
      </button>
      <EmailEditor
        ref={emailEditorRef}
        onReady={onReady}
        options={{
          projectId: 123456, // Dashboard > Project > Settings
          displayMode: 'email',
        }}
      />
    </div>
  );
};

export default EmailBuilder;

Read the full file on GitHub · 354 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 · 354 lines · 69 tokens per session scan A f29c9ce488a4

Subscribe to this mod's changes

unlayer-integration is a skill published in the GitHub repository unlayer/unlayer-skills (13 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 2,532 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories