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 rules/rendheaven/docbiz-dev-harness/frontend-workflowgit clone --depth 1 https://github.com/RendHeaven/DocBiz-Dev-HarnessWrote 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/rules/rendheaven/docbiz-dev-harness/frontend-workflow)<a href="https://agentmods.dev/rules/rendheaven/docbiz-dev-harness/frontend-workflow"><img src="https://agentmods.dev/badge/rules/rendheaven/docbiz-dev-harness/frontend-workflow.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 | $0.00000 | $0.00767 |
| Opus 5 | $0.00000 | $0.00383 |
| Sonnet 5 | $0.00000 | $0.00153 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
frontend-workflow 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 3d 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
前端工作流（DocBiz-Dev-Harness）
适用范围：globs 中的前端工程。后端只读（除非用户明确要求）。模板：features/_templates/frontend/。
P0 写入边界
- 可写： globs 内前端项目。
- 禁止写： backend-primary、backend-legacy、design-prototypes（默认只读）。
- features/ 仅在工作流要求或用户指令时编写阶段文档。
P0 总原则
- 先 plan 再码；需求未对齐禁止大改页面。
- 中间层 3 点： ① 原型 HTML（版式）② plan（语义）③ 两者约束下写代码 — 缺一不可。
- 保持项目既有技术栈与目录习惯；禁止无关重构。
目录
features/yyyyMMdd-需求简称/
├── _shared/ front-feed、task-plan、final-test …
└── {开发者标识}/
├── 1-ui-plan/plan.md
├── 2-ui-exec/task.md, exec.md
├── 3-api-plan/plan.md
└── 4-api-exec/task.md, exec.md
不产出 interface.md、front.md — 只读后端 2-exec/interface.md。
两阶段
| 阶段 | 目标 | 数据 |
|---|---|---|
| 一 UI | 可演示的界面与交互 | mock，经 src/api |
| 二 API | 替换 mock | 以后端 interface 为准 |
TASK：TASK-A.n（页面）、TASK-API.n（接口）。未就绪：[待接口]。
plan（每阶段各一份）
澄清 → 调研（代码必做；阶段一对原型 HTML；阶段二对 interface + 产品说明）→ 模板 → 用户确认 → 确认前不写业务功能。
exec
- 阶段一：mock 须在 exec 注明将替换的接口。
- 阶段二：禁止 mock 冒充联调；禁止编造字段。
- 一律 TASK 级变更，无 PATCH 捷径。
文档回写
- plan/task：按章节就地改，
<!-- 追加于 yyyy-MM-dd：原因 -->。 - exec：仅新日期段落追写。
- 阶段二回改 UI → 回写阶段一 plan/task，exec 记
[回改-来自阶段二]。
front-feed
路径 _shared/front-feed.md。联调后或跨页影响时产出。只写 UI 盲区。模板 test-feed-frontend-template.md。
纯前端需求
无后端 {标识}/ 时，在 4-api-exec/exec 贴 DevTools 抓包，供 final-test 兜底。
原型
要求参考原型时，必须打开 design-prototypes/ 下 HTML。
全文：docs/frontend-pipeline.md、docs/cross-team-rules.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.
- 3d ago First seen · 77 lines · 0 tokens per session scan A 8742d3b07445
frontend-workflow is a cursor rule published in the GitHub repository RendHeaven/DocBiz-Dev-Harness (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 767 tokens. 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.