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.
git clone --depth 1 https://github.com/zyx379/zoehis_workflowWrote 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/zyx379/zoehis_workflow/zoehis-business)<a href="https://agentmods.dev/rules/zyx379/zoehis_workflow/zoehis-business"><img src="https://agentmods.dev/badge/rules/zyx379/zoehis_workflow/zoehis-business/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/rules/zyx379/zoehis_workflow/zoehis-business"><img src="https://agentmods.dev/badge/rules/zyx379/zoehis_workflow/zoehis-business.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.00618 | $0.00618 |
| Opus 5 | $0.00309 | $0.00309 |
| Sonnet 5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
zoehis-business 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
ZOEHIS 业务规则
核心模式
池表
业务数据 → 池表(POOL)新增 → 执行后产生记录(RECORD) → 删除池表数据
主细表
- 主表
_MASTER：单据级（患者、科室、金额、状态） - 细表
_DETAIL：明细级（项目、数量、单价）
预交金
- 充值：PREPAY_RECORD(新增) + PREPAY_ACCT(更新)
- 消费：PREPAY_ACCT(更新) + CONSUME_MASTER(新增)
- 退费：PREPAY_ACCT(更新，退回)
门诊/住院对称
表名 _OUTP_ / _INP_ 区分，业务逻辑一致。
门诊处方（摘要）
保存：PRES_OUTP_PRES_MASTER + DETAIL
发送：摆药池 + 单据池；取消发送删池表
取药/执行：删池 + 记记录 + 扣预交金 + 消费流水
住院医嘱（摘要）
校对 → PRES_APPLY_RECORDS_POOL；申请 → 摆药池 + 单据池
停嘱：医生停嘱记录 → 护士审核
费用审核人与结算人分离
同一 SQL 若同时维护「业务标志」与「操作人」：
- 结算/冲销/取消锁定流程只改标志（如
FEE_AUDIT_FLAG），不改操作人（如FEE_AUDIT_OPERATOR） - 手工审核接口才更新操作人
- 涉及表：
PAT_IN_HOSPITAL.FEE_AUDIT_OPERATOR、PAT_ADMISSION_RECORD.FEE_AUDIT_OPERATOR
有效期类需求模式
系统参数 + SQL 过滤 + 执行二次校验：
- 新增系统参数（默认值 0/空 = 不限制，兼容其他医院）
- 列表/树/消息 SQL 增加时间过滤
- 执行入口增加校验方法，超时抛业务异常
- 参数 jsonl 与功能代码分 commit 提交（见 Rule
zoehis-sys-param）
关键约束
- 发送后才产生池表数据
- 执行后必须删池表并产生正式记录
- 扣费必须记消费流水；退费必须退回预交金
详细表级流转见 Skill：patterns/his-business-patterns.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.
- 10d ago First seen · 64 lines · 618 tokens per session scan A 65f4e0b9a307
zoehis-business is a cursor rule published in the GitHub repository zyx379/zoehis_workflow (2 stars, last pushed 1mo ago), licensed MIT. It adds 618 tokens to every session, about $0.0031 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.
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.