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 aemcoder/skills --skill migrate-pagegit clone --depth 1 https://github.com/aemcoder/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/aemcoder/skills/migrate-page)<a href="https://agentmods.dev/skills/aemcoder/skills/migrate-page"><img src="https://agentmods.dev/badge/skills/aemcoder/skills/migrate-page/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/aemcoder/skills/migrate-page"><img src="https://agentmods.dev/badge/skills/aemcoder/skills/migrate-page.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.00038 | $0.07215 |
| Opus 5.5 | $0.00015 | $0.02886 |
| Sonnet 5.5 | $0.00008 | $0.01443 |
| Haiku 4.5 | $0.00004 | $0.00722 |
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 1mo 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.
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. 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
-
Run
playwright-cli tab-listand find the entry withactive: true. Extract its URL. -
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"}' -
Read workspace config:
read_file /workspace/skills/migrate-page/migrate-config.jsonand parse therepofield. -
If the file is missing or
repois 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} -
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 UIwrite_file /workspace/skills/migrate-page/migrate-config.jsonwith updatedcurrentMigration— persists state for recovery
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.
- manifest.yaml 181 B
- migrate-config.json 66 B
- migrate-page.shtml 16 KB
- scripts/block-inventory.js 2.8 KB runs code
- scripts/brand-extract.js 13 KB runs code
- scripts/de-sticky.js 426 B runs code
- scripts/generate-scoop-prompts.js 6.3 KB runs code
- scripts/lazy-load-scroll.js 685 B runs code
- scripts/metadata-extract.js 1.3 KB runs code
- scripts/visual-tree.js 17 KB runs code
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.
- 1mo ago First seen · 749 lines · 38 tokens per session scan B 5f0c93048596
migrate-page is a skill published in the GitHub repository aemcoder/skills (4 stars, last pushed 1mo 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.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.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…