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/cty12356541/galideWrote 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/cty12356541/galide/style-spec-entry)<a href="https://agentmods.dev/rules/cty12356541/galide/style-spec-entry"><img src="https://agentmods.dev/badge/rules/cty12356541/galide/style-spec-entry/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/cty12356541/galide/style-spec-entry"><img src="https://agentmods.dev/badge/rules/cty12356541/galide/style-spec-entry.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.00463 | $0.00463 |
| Opus 5.5 | $0.00185 | $0.00185 |
| Sonnet 5.5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
style-spec-entry 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 2mo 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
galide 项目风格规约
本项目使用 .style-spec/ 渐进式语义规约系统。
核心原则
处理本项目任何代码前,必须先阅读 .style-spec/core/ 下的所有文件:
- core/naming.yaml — 业务实体 → 代码类型映射
- core/patterns.yaml — 通用代码模式
- core/conventions.yaml — 项目技术约定
按需读取
| 任务涉及 | 额外阅读 |
|---|---|
| 剧本编辑器 / 分支预览 | .style-spec/domain/script-editor/naming.yaml |
| 角色系统 / 立绘 | .style-spec/domain/character/naming.yaml |
| 场景 / 背景 / BGM | .style-spec/domain/scene/naming.yaml |
| 语音 / TTS | .style-spec/domain/voice/naming.yaml |
| 导出功能 | .style-spec/domain/export/naming.yaml |
| React 组件 / UI | .style-spec/layers/renderer/conventions.yaml |
| Electron 主进程 / IPC | .style-spec/layers/main-process/conventions.yaml |
| gal DSL 解析器 | .style-spec/layers/dsl/conventions.yaml |
本项目核心哲学
文字游戏 = 语言意义选项的决策树
.gal文件是 Canonical artifact,所有导出从它派生- 项目根目录即 Git 仓库根目录
- SQLite 仅存 UI 临时状态,不存决策树
- AI 是工作流的一等公民
规则优先级
core/ > layers/ > languages/,冲突时以 core/ 为准。
发现新模式
发现反复出现的模式,提案到 .auto-update/pending-proposals/。
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.
- 2mo ago First seen · 47 lines · 463 tokens per session scan A 0f83a4dac1cd
style-spec-entry is a cursor rule published in the GitHub repository cty12356541/galide (2 stars, last pushed 5d ago), licensed MIT. It adds 463 tokens to every session, about $0.0019 per session on Opus 5.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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.