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-backend-requirements-handoffgit 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-backend-requirements-handoff)<a href="https://agentmods.dev/skills/bovinphang/frontend-craft/fec-backend-requirements-handoff"><img src="https://agentmods.dev/badge/skills/bovinphang/frontend-craft/fec-backend-requirements-handoff/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-backend-requirements-handoff"><img src="https://agentmods.dev/badge/skills/bovinphang/frontend-craft/fec-backend-requirements-handoff.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.00078 | $0.00667 |
| Opus 5 | $0.00039 | $0.00333 |
| Sonnet 5 | $0.00016 | $0.00133 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
fec-backend-requirements-handoff 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 11d 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
前后端需求交接
用途
把前端页面和交互所需的数据、动作、状态和疑问整理成后端可讨论的需求说明。
流程
-
明确功能上下文
- 说明页面、流程或组件是什么，面向哪类用户，以及用户完成任务的成功状态。
- 如果已有设计稿、路由、用户故事或权限角色，先把它们作为事实来源。
-
描述前端展示需求
- 按屏幕或组件列出需要展示的信息、信息之间的关系、排序/过滤/分页需求和可见性规则。
- 使用业务语言描述“需要展示什么”，不要提前规定 endpoint、字段名、DTO、数据库表或响应嵌套结构。
-
描述用户动作和结果
- 列出用户能执行的动作、期望结果、成功反馈、失败反馈和是否需要乐观更新。
- 标出幂等性、撤销、确认、危险操作、批量操作或长任务进度等对 UI 有影响的行为。
-
补齐状态和业务规则
- 覆盖 loading、empty、error、partial、permission denied、expired、conflict、offline 和 retrying 等状态。
- 记录影响 UI 的权限、生命周期、金额/时区/枚举、校验、可编辑条件和边界规则。
-
输出讨论文档
- 默认写到
docs/backend-requirements/<feature-name>.md；若仓库已有需求文档目录，沿用现有位置。 - 文档包含 Context、Screens/Components、Data Needs、User Actions、UI States、Business Rules、Uncertainties、Questions for Backend 和 Decision Log。
- 若用户只需要聊天回复，可以直接输出同样结构的 Markdown，不创建文件。
- 默认写到
约束
- 不替后端规定 URL、HTTP 方法、字段名、数据库 schema、缓存实现或服务拆分。
- 不把前端猜测写成事实；不确定的业务规则必须进入 Uncertainties 或 Questions。
- 不忽略错误、空态、权限和部分数据；这些状态决定接口协作质量。
- 不把内部错误栈、数据库字段或敏感实现细节要求暴露给 UI。
- 不与 API 集成流程重复：本 skill 描述需求，客户端边界、类型来源和错误映射实现应在后续实现阶段处理。
预期输出
产出一份前端视角的后端需求交接说明，清楚描述 UI 需要什么数据和行为、哪些规则仍需确认，以及后续前后端需要共同决定的问题。
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.
- 11d ago First seen · 46 lines · 78 tokens per session scan A 43ca4bf03167
fec-backend-requirements-handoff is a skill published in the GitHub repository bovinphang/frontend-craft (21 stars, last pushed 10d ago), licensed MIT. It adds 78 tokens to every session and 667 once invoked, about $0.0004 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
validate-api
Run the project's Hurl scenarios with an OIDC access token passed as a secret variable.
backend-architecture
This skill should be used for consequential backend architecture decisions: module or service boundaries; modular monoliths versus independent services; service extraction and data migration; data ownership and consistency; synchronous, event-driven, actor/stateful, or pipeline designs; failure isolation…
validate-ws
Run a bounded, protocol-aware WebSocket probe with an OIDC bearer token.
dotnet-backend-expert
This skill should be used when the user is writing, reviewing, debugging, or architecting pure .NET backend code for Kestrel-hosted services. It provides expert critique for REST endpoints, SignalR hubs, TypeScript/React client integration shape, pragmatic Rust interop, application services, AppHost-aware project…
python-backend-expert
This skill should be used when the user is writing, reviewing, debugging, or architecting Python backend code using Litestar or FastAPI with SQLAlchemy or Advanced Alchemy. Provides expert critique covering SOLID principles, hexagonal architecture, repository/service patterns, dependency injection, async correctness…
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…