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-naming)<a href="https://agentmods.dev/rules/zyx379/zoehis_workflow/zoehis-naming"><img src="https://agentmods.dev/badge/rules/zyx379/zoehis_workflow/zoehis-naming/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-naming"><img src="https://agentmods.dev/badge/rules/zyx379/zoehis_workflow/zoehis-naming.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.00434 | $0.00434 |
| Opus 5 | $0.00217 | $0.00217 |
| Sonnet 5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
zoehis-naming 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 9d 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 命名规范
前端命名
- 页面目录：小驼峰 camelCase（如
hospatientDispensManage） - 组件目录：小驼峰 camelCase，与对应页面目录同名
- Vue 文件：小驼峰 camelCase（如
dateDirectInput.vue） - API 目录：短横线 kebab-case，与后端服务路径一致（如
charge-service） - API 文件：大驼峰 PascalCase，与后端 Java 类名对应（如
Laycall.js） - Mixin 文件：小驼峰 + Mixin(s) 后缀（如
printMixins.js）
后端命名
- Maven 项目：
onelink-micro-{业务域}-{地区}-{通用} - 子模块：
{父模块}-{分层}(api/pojo/service/custom) - Java 基础包：
com.zoe.optimus.service - Controller 包：
com.zoe.optimus.service.{业务域}.web.{子域} - MyBatis XML：
*Dao.xml（非*Mapper.xml） - Dao XML 路径：
mappings/{业务域}/{子域}/*.Dao.xml
数据库表命名
- 全部大写+下划线
- 前缀：
COM_公共 /PAT_患者 /CHA_收费 /PRES_处方 /APP_申请 /APT_预约 /INS_医保 /DIC_字典 - 门诊/住院：
_OUTP_/_INP_ - 主细表：
_MASTER/_DETAIL - 池表：
_POOL；记录表：_RECORD/_RECORDS
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.
- 9d ago First seen · 33 lines · 434 tokens per session scan A 0f8a88281228
zoehis-naming is a cursor rule published in the GitHub repository zyx379/zoehis_workflow (2 stars, last pushed 1mo ago), licensed MIT. It adds 434 tokens to every session, about $0.0022 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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.