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 eea/eea.agent.skills --skill plone-frontend-developergit clone --depth 1 https://github.com/eea/eea.agent.skillsWrote 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/eea/eea.agent.skills/plone-frontend-developer)<a href="https://agentmods.dev/skills/eea/eea.agent.skills/plone-frontend-developer"><img src="https://agentmods.dev/badge/skills/eea/eea.agent.skills/plone-frontend-developer/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/eea/eea.agent.skills/plone-frontend-developer"><img src="https://agentmods.dev/badge/skills/eea/eea.agent.skills/plone-frontend-developer.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.00076 | $0.01238 |
| Opus 5.5 | $0.00030 | $0.00495 |
| Sonnet 5.5 | $0.00015 | $0.00248 |
| Haiku 4.5 | $0.00008 | $0.00124 |
Grade A, and why
plone-frontend-developer 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 19d 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plone Frontend Developer
Overview
Diagnose and fix Plone/Volto frontend issues in any EEA frontend, whether it is a full Volto project or a reusable add-on. EEA frontends come from more than one template generation, so their layout and commands differ. Discover the project first instead of assuming paths or targets.
For Cypress-specific work, use the volto-cypress-writer skill.
Discover the project first
Before editing, read:
- the project
AGENTS.mdfor project-specific conventions and dev environment Makefile— runmake helpto see the real targetspackage.json—addons,resolutions, thevoltodependency, test scriptsvolto.config.js— the registered add-onsmrs.developer.json— add-ons mounted in development mode
Use references/volto-project-layouts.md to map what you find to one of the known
EEA generations (legacy add-on, Cookieplone add-on, Cookieplone project).
Core workflow
- Clarify the symptom, the affected URL, and the expected behavior. Note the language/locale if the site is multilingual.
- Locate the code path:
src/,packages/<addon>/src/, orsrc/addons/<addon>/src/, depending on the generation. - Reproduce and isolate: make minimal changes, add short-lived logs if needed, and confirm the exact component/block responsible.
- Implement the fix in the most appropriate layer (project or add-on). Favor design tokens and shared helpers over hard-coded values.
- Verify with the smallest relevant check (unit test, lint, typecheck, or a targeted runtime check) and report what you ran.
Common tasks
- Add-on debugging: find the add-on in the project's add-on registry
(
volto.config.js,package.jsonaddons, ormrs.developer.json), then trace the component to its package. - Blocks/components: check both the edit and the view components; cover the edit-time behavior and the saved output.
- Theme/tokens: replace hard-coded values with design tokens and update
shared theme/config entries to keep consistency. See the
eea-design-systemskill. - i18n: define messages in the add-on/project, then run the project's i18n
target (
make i18n). - Routing/multilingual links: check locale-aware routing and URL generation before hardcoding language paths.
What ships with it
1 file 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.
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.
- 19d ago First seen · 129 lines · 76 tokens per session scan A a18b2eee37eb
plone-frontend-developer is a skill published in the GitHub repository eea/eea.agent.skills (5 stars, last pushed 20d ago), licensed MIT. It adds 76 tokens to every session and 1,238 once invoked, about $0.0003 per session on Opus 5.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-09-28.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…