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/meishanlaoyao/elysia-adminWrote 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/meishanlaoyao/elysia-admin/backend)<a href="https://agentmods.dev/rules/meishanlaoyao/elysia-admin/backend"><img src="https://agentmods.dev/badge/rules/meishanlaoyao/elysia-admin/backend/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/meishanlaoyao/elysia-admin/backend"><img src="https://agentmods.dev/badge/rules/meishanlaoyao/elysia-admin/backend.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.00000 | $0.02157 |
| Opus 5.5 | $0.00000 | $0.00863 |
| Sonnet 5.5 | $0.00000 | $0.00431 |
| Haiku 4.5 | $0.00000 | $0.00216 |
Grade A, and why
backend 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Module Structure
Every module under server/src/modules/{group}-{name}/ should contain:
modules/{group}-{name}/
dto.ts ← Elysia validation + route DTO fragments; optional afterHandle hooks
handle.ts ← business logic only
route.ts ← HTTP mapping only
task.ts ← BullMQ / sandbox worker exports (optional; omit if no tasks)
No extra files. No renaming. Routes auto-register on startup.
task.ts: add only when registering queue/cron jobs in server/src/worker-sandbox/.
Cross-module handle (Cross-Table Data Access):
- Each module may directly query only its own table schemas.
- To access another module's table, call the owning module's exported PascalCase function from its
handle.ts— do NOT import that module's@database/schema. - Route handlers = lower camelCase (
create,findList); cross-module exports = PascalCase (GetUserBy,GetDeptInfoById). - If the helper is missing, add it in the owning module first, then import it from the consumer.
- New business modules should stay self-contained; avoid mesh dependencies.
Layer Rules (Strict)
| File | Allowed | Forbidden |
|---|---|---|
dto.ts |
Elysia schema, response DTO, optional hooks | complex orchestration, direct DB |
handle.ts |
own-module schema + repository, QueryBuilder, shared, infrastructure; other modules' exported handle functions | raw SQL, direct pg, new Elysia in handle, importing other modules' @database/schema for cross-table queries |
route.ts |
bind dto+handle, return result | business logic, DB access |
task.ts |
export plain functions, call handle | duplicate business logic, direct DB |
Repository Functions (from @/core/database/repository)
InsertOne(schema, ctx) // insert, no return
InsertOneAndRes(schema, ctx) // insert, return record
InsertMany(schema, ctx, dataArray) // bulk insert
FindOneByKey(schema, 'primaryKey', value) // find by key
FindAll(schema, whereSQL, options?) // find all (no pagination)
FindPage(schema, whereSQL, paginationOptions) // paginated query
UpdateByKey(schema, 'primaryKey', ctx) // update by key
UpdateByKeyAndRes(schema, 'primaryKey', ctx) // update, return record
SoftDeleteByKeys(schema, 'primaryKey', ctx) // soft delete (sets delFlag=true)
HardDelete(schema, whereSQL) // permanent delete
HardDeleteByKeys(schema, 'primaryKey', values) // permanent delete by keys
FindAllWithJoin(schema, builder, options?) // find all with join
FindPageWithJoin(schema, builder, options) // paginated with join
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.
- 1mo ago Changed · +13 lines 79af7d436111
- 1mo ago First seen · 191 lines · 0 tokens per session scan A 6bf308b96faa
backend is a cursor rule published in the GitHub repository meishanlaoyao/elysia-admin (53 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,157 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-30.
Other cursor rules, from other repositories
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
server-state
USE WHEN: Fetching and caching server data with TanStack Query 5: queryOptions, hooks, mutations, invalidation.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.