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/legacy-migrationgit 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/legacy-migration)<a href="https://agentmods.dev/rules/rendheaven/docbiz-dev-harness/legacy-migration"><img src="https://agentmods.dev/badge/rules/rendheaven/docbiz-dev-harness/legacy-migration.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.00030 | $0.00336 |
| Opus 5 | $0.00015 | $0.00168 |
| Sonnet 5 | $0.00006 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
legacy-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 5d 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
旧栈 API 迁移专项（DocBiz-Dev-Harness）
backend-workflow.mdc 的补充。适用于 /legacy-api/* → /api/* 重写。
不适用
- 仅主栈内重构
- 纯前端调整
- 无旧实现的新功能
流程嵌入
| 阶段 | 额外动作 |
|---|---|
| 1-plan | 前端使用表、字段精简、复刻vs优化、归属、路径映射 |
| 2-exec | 差异注释、命名、沉 shared-service |
| 4-interface-test | CASE-COMPARE-N |
| 5-api-doc | 迁移自 + 字段差异 |
| 养料/终测 | 路径/删字段/重命名可执行用例 |
字段精简
保留：前端真用、标识/状态。删除：无引用、调试字段。有疑义问人。
前端
搜 legacy 路径与 API 函数引用；整理字段清单给后端写入 interface；联调阶段切路径。
rg "legacy-api路径片段" web-app/src/api/
rg "api函数名" web-app/src/
全文：docs/migration-addon.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.
- 5d ago First seen · 40 lines · 30 tokens per session scan A 3322cf9708d9
legacy-migration is a cursor rule published in the GitHub repository RendHeaven/DocBiz-Dev-Harness (2 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 336 once invoked, about $0.0002 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.