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 bovinphang/frontend-craft --skill fec-legacy-to-modern-migrationgit clone --depth 1 https://github.com/bovinphang/frontend-craftWrote 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/bovinphang/frontend-craft/fec-legacy-to-modern-migration)<a href="https://agentmods.dev/skills/bovinphang/frontend-craft/fec-legacy-to-modern-migration"><img src="https://agentmods.dev/badge/skills/bovinphang/frontend-craft/fec-legacy-to-modern-migration/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/bovinphang/frontend-craft/fec-legacy-to-modern-migration"><img src="https://agentmods.dev/badge/skills/bovinphang/frontend-craft/fec-legacy-to-modern-migration.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.00097 | $0.01040 |
| Opus 5 | $0.00048 | $0.00520 |
| Sonnet 5 | $0.00019 | $0.00208 |
| Haiku 4.5 | $0.00010 | $0.00104 |
Grade A, and why
fec-legacy-to-modern-migration 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 12d 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.
What it actually says
传统前端到现代框架迁移
适用于将 JavaScript + jQuery + HTML/CSS 多页面应用（MPA）、服务端模板渲染项目或旧框架代码，渐进迁移到 React、Vue、Next.js、Nuxt、TypeScript，或保留 MPA 形态但现代化模块、构建、类型和测试的场景。
用途
指导传统前端项目渐进迁移到目标现代栈，提供迁移策略、概念映射、分阶段步骤和实施约束，确保功能等价和风险可控。
流程
- 先识别目标栈、迁移边界和是否保留 MPA/服务端模板形态。
- 加载 references/migration-strategy-and-mapping.md，选择渐进式或一次性重写策略，并明确遗留模式到目标栈的映射。
- 加载 references/migration-execution-checklist.md，完成存量盘点、依赖分析、优先级排序和分阶段迁移计划。
- 撰写迁移分析或迁移计划报告时，加载 references/migration-report-template.md。
- 按准备、基础层、模块/页面迁移、收尾的顺序推进，每次迁移一个可验证单元。
- 每个迁移单元验证功能等价、视觉一致、类型安全、可访问性、i18n、资源和样式边界。
约束
- 迁移前必须先输出迁移分析报告，明确策略、优先级和风险。
- 不要在一次迁移中同时改架构、改 UI、改接口。
- 优先保证功能等价，再考虑优化和现代化。
- 迁移过程中保持旧系统可运行，避免大爆炸式上线。
- 遇到 jQuery 插件无现成替代时，可暂时用 iframe 或微前端方式嵌入，待后续替换。
- 目标栈先识别 React/Vue/Next/Nuxt、现代 MPA 或局部现代化目标，不默认强制改成 SPA。
- 图片使用原项目资源；图标体系优先沿用原项目或目标项目规范；内联 SVG 例外需有可访问性、组件化或维护理由。
- 样式参考原项目效果但不照搬 CSS，优先使用目标项目样式体系；内联样式例外需局部、可解释。
- 目标是视觉与交互一致、代码更简洁易维护，业务功能不得缺失。
- 涉及页面、组件、路由、表单、弹窗、导航或关键用户流程的迁移，必须建立重构前后的行为清单，并使用 Playwright 或同等真实浏览器验证方式对关键路径做对比验证。
- 对视觉敏感页面，应补充截图对比或人工截图验收；动态内容、动画、字体和环境差异需明确屏蔽、稳定化或说明。
- 对纯逻辑、类型、构建或无 UI 的迁移，不强制 Playwright，应选择更贴近风险的验证层：type-check、unit test、component test、build 或 lint。
- 验证目标不是像素级完全一致，而是确认业务功能无缺失、关键交互等价、主要视觉布局无非预期偏差，并且代码比旧实现更清晰、可维护。
预期输出
- 迁移分析报告保存为
reports/migration-plan-YYYY-MM-DD-HHmmss.md，包含策略选择、存量盘点、依赖关系、分阶段步骤、风险与回滚方案。 - 迁移后的业务功能与原项目完全等价，无功能缺失。
- 视觉与交互与原项目一致，用户无感知差异。
- 类型定义完整，无
any滥用，API 调用统一且类型安全。 - 图片使用原项目资源，样式进入目标项目样式体系，图标和内联样式例外有明确理由。
- 新代码文案已 i18n，关键路径有测试覆盖。
What ships with it
3 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.
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.
- 12d ago First seen · 47 lines · 97 tokens per session scan A a7687fd96971
fec-legacy-to-modern-migration is a skill published in the GitHub repository bovinphang/frontend-craft (21 stars, last pushed 11d ago), licensed MIT. It adds 97 tokens to every session and 1,040 once invoked, about $0.0005 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.
Other skills, from other repositories
mobile-flows-maestro
This skill should be used when Maestro is explicitly requested or already present and the task is to author, run, or debug iOS/Android Maestro flows; use Maestro MCP; or handle Maestro selectors, system UI, permissions, Keychain, JavaScript, waits, device state, flakiness, or CI. Evidence includes a .maestro directory…
brand-design
Brand-aware design system generator that acts as Head of Brand. Translates abstract brand language into a mathematically-validated, implementation-ready design system, writes creative-brief.md as the source of truth for all UI/UX in a project, and optionally compiles it to framework tokens (Tailwind v4 @theme, v3…
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
skeptical-triage
Reusable 3-round self-challenge + arbiter pattern for filtering false positives from findings/verdicts. Use when the cost of a false-positive gate block exceeds the cost of 4 extra LLM turns.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.