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-db-tables)<a href="https://agentmods.dev/rules/zyx379/zoehis_workflow/zoehis-db-tables"><img src="https://agentmods.dev/badge/rules/zyx379/zoehis_workflow/zoehis-db-tables/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-db-tables"><img src="https://agentmods.dev/badge/rules/zyx379/zoehis_workflow/zoehis-db-tables.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.00305 | $0.00305 |
| Opus 5 | $0.00152 | $0.00152 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
zoehis-db-tables 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 数据库表规范
表名规则
- 大写+下划线：
{前缀}_{OUTP|INP}_{业务名}_{后缀} - 前缀：COM_ / PAT_ / CHA_ / PRES_ / APP_ / APT_ / INS_ / DIC_
- 后缀：_MASTER / _DETAIL / _POOL / _RECORD / _DICT
核心表（节选）
患者： PAT_BASIC_INFO, PAT_IN_HOSPITAL, PAT_OUTP_PATIENT_CLINIC_INFO
处方： PRES_OUTP_PRES_MASTER/DETAIL, PRES_INP_PRES_RECORD, PRES_APPLY_RECORDS_POOL
摆药/单据： APP_LAY_DRUG_POOL/RECORDS, APPAPPLY_SHEET_POOL, APP_RETURN*
收费： CHA_PREPAY, CHA_CHARGE_DETAIL, CHASETTLE_MASTER, INS*_SETTLE_MASTER
字典： DIC_DRUG_DICT, DIC_BED_DICT, DIC_PAY_MODE_DICT, DIC_CLINIC_ITEM_DICT
完整清单见原规范；新增表须符合前缀与门诊/住院对称约定。
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 · 27 lines · 305 tokens per session scan A b9e8ecd495e3
zoehis-db-tables is a cursor rule published in the GitHub repository zyx379/zoehis_workflow (2 stars, last pushed 1mo ago), licensed MIT. It adds 305 tokens to every session, about $0.0015 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
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
postgresql
This guide defines the definitive best practices for writing clean, performant, and maintainable PostgreSQL SQL, focusing on modern conventions and avoiding common pitfalls.
query-optimization
A database performance rule that requires measuring PostgreSQL queries with EXPLAIN ANALYZE under the same user permissions and row-level security (RLS) conditions used in production.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.