agentmods.dev

migrate-page

A workflow for moving a web page into AEM Edge Delivery Services, Adobe’s system for building and delivering websites from structured content. It breaks the page into reusable blocks, creates the matching code, and checks the visual result.

In plain words
What is it for?
It is for converting a page from a URL into EDS blocks in a GitHub repository and verifying the migrated page visually.
Why use it?
It removes the manual work of turning an existing page into the format AEM Edge Delivery Services expects while checking that the result still looks right.

Skill for Claude CodeCodex

2 5d ago B scan 38 tokens original Apache-2.0
View the source file aemcoder/skills
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.

agentmods
npx agentmods add skills/aemcoder/skills/migrate-page
Any agent
npx skills add aemcoder/skills --skill migrate-page
Clone the repo
git clone --depth 1 https://github.com/aemcoder/skills

Made for: Claude Code, Codex.

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,215 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. Scan, not verified.
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 $0.00038 $0.07215
Opus 5 $0.00019 $0.03608
Sonnet 5 $0.00008 $0.01443
Haiku 4.5 $0.00004 $0.00722

Measured 2d ago against content hash 5f0c93048596, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

migrate-page scanned grade B with 2 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 2d ago.

The scan reads SKILL.md. This mod also ships 7 executable files (scripts/block-inventory.js, scripts/brand-extract.js, scripts/de-sticky.js, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

> six near-simultaneous sudo requests that stall the batch until approved.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

> - `child_process` `spawn*`/`exec*` — not available in the bridge realm.
skills/migration/migrate-page/SKILL.md · 749 lines

How it starts

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

EDS Page Migration

Migrate a web page into AEM Edge Delivery Services: extract structure, decompose into blocks, generate EDS-compatible code per block, and verify each with visual comparison.

IMPORTANT: Cone-Only Skill

This skill MUST be executed by the cone directly. Do NOT delegate the migration to a scoop. The cone runs Phases 1–2.5 and 4 itself. Only Phase 3 (block generation) creates scoops — one per block. Scoops cannot create other scoops, so the cone must be the orchestrator.

Triggers

"migrate this page", "convert to EDS", "create EDS blocks from URL". User provides a URL and a GitHub repo (owner/repo).

Sprinkle Trigger

When this skill is triggered via a sprinkle lick event (type sprinkle, skill migrate-page), the cone handles the lick directly and runs sprinkle send commands. This overrides Rules 2 and 5 in /shared/CLAUDE.md — the cone MUST handle this lick itself because it creates scoops in Phase 3 (scoops cannot create scoops), making the cone the only viable orchestrator.

Lick Handling

  1. Run playwright-cli tab-list and find the entry with active: true. Extract its URL.

  2. If no active HTTP(S) tab exists, send an error and stop:

    sprinkle send migrate-page '{"phase":"error","message":"No page to migrate — navigate to a webpage first"}'

  3. Read workspace config: read_file /workspace/skills/migrate-page/migrate-config.json and parse the repo field.

  4. If the file is missing or repo is empty, ask the user in chat for the repo, then write the config:

    write_file /workspace/skills/migrate-page/migrate-config.json
{"repo":"owner/repo-name","currentMigration":null}

  5. Start Phase 1 with the extracted URL and repo.

Progress Reporting

At each phase transition, run BOTH:

  • sprinkle send migrate-page '<json>' — updates the live sprinkle UI
  • write_file /workspace/skills/migrate-page/migrate-config.json with updated currentMigration — persists state for recovery

Read the full file on GitHub · 749 lines

Files

What ships with it

10 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. 2d ago First seen · 749 lines · 38 tokens per session scan B 5f0c93048596

Subscribe to this mod's changes

migrate-page is a skill published in the GitHub repository aemcoder/skills (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 38 tokens to every session and 7,215 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Frontend
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens