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/Siborne/YiSmart-CloudWrote 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/siborne/yismart-cloud/front-api-and-config-conventions)<a href="https://agentmods.dev/rules/siborne/yismart-cloud/front-api-and-config-conventions"><img src="https://agentmods.dev/badge/rules/siborne/yismart-cloud/front-api-and-config-conventions.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.00000 | $0.00313 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
front-api-and-config-conventions 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 7d 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 与配置约定（YiSmartCloud）
- 路由：业务菜单与路由主要由后端菜单数据动态下发（若依惯例），日常增页优先走菜单配置；非必要不要依赖大量手写静态路由。
- API 文件放在
src/api/<module>/，函数命名使用listX/getX/addX/updateX/delX，与页面调用保持一一对应。 - 统一使用
@/utils/request，请求体字段使用params（GET）或data（POST/PUT），URL 保持 REST 风格。 - 导出接口走后端
/export路径，并与页面proxy.download使用的资源路径一致。 - 字符串风格、注释风格与现有代码保持一致：中文注释说明接口用途，避免引入与仓库不一致的新抽象层。
vite.config.js延续当前别名与代理写法：@ -> ./src，/dev-api代理后端，变更需保证本地开发可直连。- 新增配置优先最小改动，不随意重排现有键顺序，避免产生大量无意义 diff。
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.
- 7d ago First seen · 14 lines · 0 tokens per session scan A 934658077729
front-api-and-config-conventions is a cursor rule published in the GitHub repository Siborne/YiSmart-Cloud (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 313 tokens. 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
project
Development rules for uni-app projects built with Vue 3 and TypeScript. uni-app is a framework for creating H5 websites, mini-programs, and mobile apps from one codebase.
vue
A set of Vue 3 and uni-app coding rules covering components, naming, props, APIs, TypeScript, and Pinia state management.
pages
Source: docs/agents/pages.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
react-basics-state
A set of React rules for managing shared application state with Context API and useReducer. React is a JavaScript library for building user interfaces; shared state is information used by multiple parts of an interface.