elementor-v3-widget-controls

elementor-v3-widget-controls is a skill for Codex from Lonsdale201/wp-agent-skills. It costs 121 tokens per session (2,888 once invoked), scanned A, original, MIT.

A guide to configuring the built-in controls of classic Elementor widgets. These controls are the editor fields used for content, styles, responsive settings, links, images, icons, and repeated items.

In plain words
What is it for?
Use it when implementing or reviewing a WidgetBase control panel, including responsive values, repeaters, dynamic tags, conditions, selectors, media, URLs, and icons.
Why use it?
It helps ensure that saved control values match what the widget's rendering code expects. It also distinguishes Elementor's editor controls from security sanitizers and from the newer Atomic Widgets system.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it when implementing or reviewing a WidgetBase control panel, including responsive values, repeaters, dynamic tags, conditions, selectors, media, URLs, and icons.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lonsdale201/wp-agent-skills/elementor-v3-widget-controls
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 Lonsdale201/wp-agent-skills --skill elementor-v3-widget-controls
Clone the repo
git clone --depth 1 https://github.com/Lonsdale201/wp-agent-skills

Made for: 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 elementor-v3-widget-controls

README.md
[![agentmods](https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/elementor-v3-widget-controls/github.svg)](https://agentmods.dev/skills/lonsdale201/wp-agent-skills/elementor-v3-widget-controls)
Your own site
<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/elementor-v3-widget-controls"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/elementor-v3-widget-controls/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.

agentmods 80×15 button for elementor-v3-widget-controls

Your own site · 80×15
<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/elementor-v3-widget-controls"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/elementor-v3-widget-controls.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 121 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,888 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00121 $0.02888
Opus 5 $0.00060 $0.01444
Sonnet 5 $0.00024 $0.00578
Haiku 4.5 $0.00012 $0.00289

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

Security

Grade A, and why

elementor-v3-widget-controls 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 11d 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.

elementor/elementor-v3-widget-controls/SKILL.md · 239 lines

How it starts

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

Elementor V3 widget controls

Build editor panels from Elementor's built-in classic controls and couple each saved value to safe, predictable rendering. “V3” means the established Widget_Base / Controls_Stack model even when the installed plugin is Elementor 4.x. Do not apply these arrays to Atomic Widgets / Editor V4.

This skill does not create custom control types. Prefer a built-in control or a well-defined fallback; a custom-control integration is a separate lifecycle, asset, and compatibility problem.

When to use this skill

  • Add or review register_controls() in a Widget_Base subclass.
  • Choose between regular, responsive, group, repeater, media, URL, or icon controls.
  • Use selectors, selectors_dictionary, prefix_class, condition, or conditions.
  • Diagnose a control that saves one shape but render() expects another.
  • Enable dynamic tags or expose selected settings to widget JavaScript.
  • Render repeater rows, responsive values, links, icons, or editor-inline text.
  • Audit whether Elementor controls are being mistaken for sanitizers.

Read references/built-in-controls-and-patterns.md when implementing value shapes, selector tokens, group controls, repeaters, or a full example. Pair this skill with elementor-v3-widget-development for bootstrap, registration, assets, caching, and frontend lifecycle.

Workflow

1. Start from output and data shape

Before adding panel fields, write down:

  1. The semantic output and accessibility behavior.
  2. The exact saved value shape: scalar, compound array, list, or responsive variants.
  3. The final output context and validation allowlist.
  4. Whether a style can be expressed through Elementor selectors or needs PHP/JS.
  5. Whether the value may use a dynamic tag.

Do not choose a control by appearance alone. A URL, MEDIA, ICONS, SLIDER, DIMENSIONS, and REPEATER each returns a structured array, not a string.

2. Put controls in explicit sections

Classic widget controls must be inside a section:

Read the full file on GitHub · 239 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 239 lines · 121 tokens per session scan A fdb49a372d3d

Subscribe to this mod's changes

elementor-v3-widget-controls is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (22 stars, last pushed today), licensed MIT. It adds 121 tokens to every session and 2,888 once invoked, about $0.0006 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

playground

Creates interactive HTML playgrounds — self-contained single-file explorers that let users configure something visually through controls, see a live preview, and copy out a prompt. Use when the user asks to make a playground, explorer, or interactive tool for a topic.

anthropics/claude-plugins-official · 53 tokens

frontend-design

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

anthropics/claude-plugins-official · 40 tokens

fixing-accessibility

Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.

ibelick/ui-skills · 45 tokens

baseline-ui

Quickly deslop UI code by fixing spacing, hierarchy, typography, and small layout issues. Use when the interface needs a fast cleanup or polish pass.

ibelick/ui-skills · 34 tokens

generative-ui

Design system and guidelines for Claude's built-in generative UI — the showwidget tool that renders interactive HTML/SVG widgets inline in claude.ai conversations. This skill provides the complete Anthropic "Imagine" design system so Claude produces high-quality widgets without needing to call readme first. Use this…

himself65/finance-skills · 205 tokens

accessibility

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

addyosmani/web-quality-skills · 51 tokens