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 agentmods add skills/movebrickschi/harness-engineering-mcp/dev-flow-proto-fenpx skills add movebrickschi/harness-engineering-mcp --skill dev-flow-proto-fegit clone --depth 1 https://github.com/movebrickschi/harness-engineering-mcpWrote 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/movebrickschi/harness-engineering-mcp/dev-flow-proto-fe)<a href="https://agentmods.dev/skills/movebrickschi/harness-engineering-mcp/dev-flow-proto-fe"><img src="https://agentmods.dev/badge/skills/movebrickschi/harness-engineering-mcp/dev-flow-proto-fe.svg" alt="Measured on agentmods" 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.00119 | $0.01657 |
| Opus 5 | $0.00060 | $0.00829 |
| Sonnet 5 | $0.00024 | $0.00331 |
| Haiku 4.5 | $0.00012 | $0.00166 |
Grade A, and why
dev-flow-proto-fe 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 6d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dev-flow-proto-fe
适用场景
- PM 提供参考项目 A（可运行）
- B 项目只做前端
- 后端接口由别人实现或已存在
前置条件
确认 _playbook.md Part B.3 启动参数；额外需要 prototype_path 与 prototype_url。通常由父 skill /dev-flow 通过 dispatch-context.json 传入。
流程步骤
本 skill 是
/dev-flow-full的"前端裁剪版"。可直接调用/dev-flow-full并传入scope=fe让其内部裁剪，也可按以下步骤手动执行。
阶段 0 · 上下文初始化
同 /dev-flow-full 阶段 0：建知识库目录、写 META.md、加载 _lessons.md。
阶段 1 · A 项目探索（A 只读）
move_agent_to_root切到 A 项目- 立即
/freeze锁定 A 根目录 SwitchMode→ plan- 用
cursor-ide-browserMCP 走查目标 URL：browser_snapshot抓页面结构browser_take_screenshot全页截图- 依次点击所有可交互元素
browser_network_requests抓 API（用于反推后端契约，作为输入约束）browser_console_messages检查报错
- 并行派发 2 个 explore subagent（跳过后端 subagent）：
- Task A：项目骨架（技术栈、目录结构、入口文件、构建脚本）
- Task B：前端实现（路由、组件、状态管理、API 调用层）
- 输出抽象化文档：
BUSINESS_FLOW.md（业务流程，禁含具体代码）API_CONTRACT.md（输入契约，约束 B 项目实现的对接方式）ENV_NOTES.md（A 运行环境特征）
阶段 2 · 需求澄清（卡点 1）
按 _playbook.md Part B.2 卡点 1，循环到无疑问。
阶段 3 · B 项目勘察
move_agent_to_root切到 B 项目SwitchMode→ agent- 并行 2 个 explore subagent（跳过后端横切）：
- 前端骨架（技术栈、目录结构、构建/启动、代码规范、git 工作流）
- 前端类似功能复用审计（已有的页面/组件模板在哪）
- 输出
PROJECT_CONVENTIONS.md+REUSE_AUDIT.md
阶段 4 · 方案设计（卡点 2）
git checkout -b feature/[feature]- 只出前端
IMPLEMENTATION_PLAN.md：A 概念到 B 实现的翻译映射 + 新建/修改文件清单 /plan-eng-review→ 卡点 2
阶段 5 · 垂直切片（卡点 3）
- 选最具代表性的端到端场景（通常列表 or 详情）
- 实现最小切片：1 个页面对接 1 个真实接口
- 原子 commit → 卡点 3
阶段 6 · 水平铺开
frontend-agent：剩余页面test-agent：交互/路由/表单测试
阶段 7 · 自查
/qa、/review、/design-review必做/cso可选（无后端改动通常不需要）
阶段 8 · PM 验收（卡点 4）
demo-package.md 必含与原型 A 的行为对比表与已知差异说明。
阶段 9–10 · 上线 + 复盘
/ship → /land-and-deploy → /canary → append _lessons.md。
错误处理
- 依赖的后端接口不存在 / 行为不符 → 退出裁剪，升级到
/dev-flow-full（S6） - A 项目无法访问/启动 → 报告问题，等待用户提供帮助
- A 与 B 的字段命名差异过大 → 在
IMPLEMENTATION_PLAN.md显式列出映射表
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.
- 6d ago First seen · 126 lines · 119 tokens per session scan A 94f63a3944f3
dev-flow-proto-fe is a skill published in the GitHub repository movebrickschi/harness-engineering-mcp (2 stars, last pushed 3mo ago), licensed MIT. It adds 119 tokens to every session and 1,657 once invoked, about $0.0006 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-31.
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…
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.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
prototype-web
可点击的功能性 Web 原型, 含导航、英雄区、特性区、CTA.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…
vite
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.