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-alchemygit 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-alchemy)<a href="https://agentmods.dev/skills/bovinphang/frontend-craft/fec-alchemy"><img src="https://agentmods.dev/badge/skills/bovinphang/frontend-craft/fec-alchemy/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-alchemy"><img src="https://agentmods.dev/badge/skills/bovinphang/frontend-craft/fec-alchemy.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.00051 | $0.01168 |
| Opus 5 | $0.00026 | $0.00584 |
| Sonnet 5 | $0.00010 | $0.00234 |
| Haiku 4.5 | $0.00005 | $0.00117 |
Grade A, and why
fec-alchemy 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 10d 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
项目吸收与原创化融合
用途
将一个或多个参考系统中的优秀思想、能力和工程实践，转化为当前项目中原创、可维护、符合目标项目风格的改进。
适用于吸收、借鉴、对标、迁移或融合另一个代码库、产品、框架、库、服务、CLI、插件、文档体系、AI/Agent 工具链、架构或工程工作流。普通 Bug 修复、单独 API 使用问题或直接文件格式转换不应使用本 Skill，除非用户明确要求项目级吸收或适配。
流程
- 明确目标和参考系统：
- 将当前仓库视为目标系统，它的架构、命名、测试、发布模型和维护边界是事实来源。
- 将外部仓库、上传压缩包、文档、示例、产品描述或运行体验视为参考系统，它们只提供证据和启发。
- 识别吸收范围：产品能力、架构模式、领域模型、接口协议、数据流、运行时行为、开发体验、质量体系、交付流程、文档知识或生态扩展。
- 信息较多时可使用 assets/intake-template.md 建立简要清单。
- 建立目标项目基线：
- 先读取目标项目 README、包元数据、目录结构、配置、现有入口、扩展点、测试命令和发布说明。
- 找出目标项目已有类似能力，判断应增强、合并、替换、拆分、文档化还是新增。
- 扫描参考项目：
- 优先查看 README、包元数据、源码布局、项目形态相关目录、关键模块、测试、示例和发布说明。
- 将观察记录为能力、意图、模式和取舍，不记录为要复制的文件清单。
- 提炼候选能力：
- 对每个候选项说明它解决的问题、用户价值、适配度、依赖、风险、可验证性和与目标项目现状的关系。
- 对许可证、来源不清楚或实现高度绑定参考项目的候选项，只提炼思想，不复用表达。
- 映射到目标架构：
- 使用目标项目原生命名、模块边界、依赖策略、编码约定和测试方式重新设计。
- 避免创建与现有模块竞争的并行系统；避免因为参考项目用了某依赖就盲目引入依赖。
- 非平凡变更可使用 assets/absorption-plan-template.md。
- 原创化实现或计划：
- 编写新代码或新文档，不复制参考项目中的非平凡代码、提示词、配置或文档表达。
- 吸收生态扩展、提示词、命令、插件、自动化、Agent 或规则时，统一职责边界并删除重复指令。
- 大型任务先交付垂直薄切片，并记录被拒绝或延期的候选项。
- 验证和汇报：
- 运行最相关的类型检查、Lint、测试、构建、文档校验或 Skill 校验。
- 如果无法验证，明确说明阻塞原因、风险范围和需要用户确认的信息。
- 必要时使用 assets/review-checklist.md 做人工复核。
约束
- 不把吸收任务变成机械化 diff 合并。
- 不整体照搬参考项目的命名体系、文件结构或实现细节。
- 不在许可证或用户意图不明确时逐字复用参考项目中的非平凡代码、文档、提示词或配置。
- 不为了匹配参考项目而削弱安全、隐私、权限边界、测试、可维护性或目标项目产品方向。
- 不声称原创化，除非输出能解释目标设计为何不同、为何适配目标项目、如何验证。
- 不把长篇参考材料塞进主说明；大型任务读取 references/methodology.md，许可证和原创风险读取 references/originality-and-licensing.md。
预期输出
分析类任务输出：
- 吸收候选项
- 推荐目标设计
- 实现计划
- 风险与许可证说明
- 验证清单
实现类任务输出：
- 已完成变更
- 原创化说明
- 验证结果
- 剩余工作
仓库级任务中，如果宿主工具支持文件编辑，应创建或更新项目本地计划文档。
详细参考
- references/methodology.md - 详细吸收方法论。
- references/originality-and-licensing.md - 原创性、许可证和来源风险约束。
What ships with it
5 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.
- 10d ago First seen · 75 lines · 51 tokens per session scan A 6c82b8eef96e
fec-alchemy is a skill published in the GitHub repository bovinphang/frontend-craft (21 stars, last pushed 8d ago), licensed MIT. It adds 51 tokens to every session and 1,168 once invoked, about $0.0003 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
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.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
techdebt
Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.