What is elysia-module-dev?

A full-stack development checklist for adding modules to an Elysia Admin application. It covers backend and admin-page code, database tables, menus, permissions, dictionaries, and handoff SQL.

Use it when creating CRUD features, admin pages, database schemas, role-based access controls, or menu and dictionary entries.

It helps developers follow the project's required order and conventions instead of missing setup or producing code that does not fit the existing system.

How meishanlaoyao/elysia-admin configures Cursor

Reuse

Borrowing it

Nothing to install: this file belongs to meishanlaoyao/elysia-admin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/meishanlaoyao/elysia-admin/master/.cursor/skills/elysia-module-dev/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/meishanlaoyao/elysia-admin

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/meishanlaoyao/elysia-admin/elysia-module-dev/github.svg)](https://agentmods.dev/skills/meishanlaoyao/elysia-admin/elysia-module-dev)

Your own site

<a href="https://agentmods.dev/skills/meishanlaoyao/elysia-admin/elysia-module-dev"><img src="https://agentmods.dev/badge/skills/meishanlaoyao/elysia-admin/elysia-module-dev/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/meishanlaoyao/elysia-admin/elysia-module-dev"><img src="https://agentmods.dev/badge/skills/meishanlaoyao/elysia-admin/elysia-module-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,779 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00067	$0.01779
Opus 5.5	$0.00027	$0.00712
Sonnet 5.5	$0.00013	$0.00356
Haiku 4.5	$0.00007	$0.00178

Measured 1mo ago against content hash e72898f21cc6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

elysia-module-dev 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.

.cursor/skills/elysia-module-dev/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Elysia Admin Module Development

Follow this checklist; read .ai/ docs for details. NEVER skip steps.

When to Use

New server/src/modules/{group}-{name}/
New admin/src/views/{group}/{name}/
Menu, button permissions, or data dict required
Database schema design or verification

Triggers: CRUD module, business-*, menu permission, handoff sql, schema design, admin page

User phrases (中文): 按 module dev workflow, 走完整 SOP, 含菜单权限和 handoff SQL, 全栈模块, 先用脚手架, 脚手架已生成

Large / multi-module first: If the request names multiple business feature modules or a full project, follow .ai/AI_PHASED_TASKS.md and write a task pack under this IDE’s feature-tasks/{slug}/ before running this Skill for any single module.

10-Step Checklist

1. MCP

MUST use Postgres MCP read-only for tables, dict, menu IDs (.ai/AI_MCP_SETUP.md) — first for runtime data
NEVER read or modify server/database/sql/pg.sql (stale backup only; use MCP or schema files)
If unavailable: declare fallback; use SQL subqueries or placeholders

2. Schema

MUST check server/database/schema/ first
Main table: ...BaseSchema; sort field name MUST be sort
Pure junction table: two FKs only; hard delete
Soft delete & unique: new unique constraints → partial unique index WHERE del_flag = false (not column .unique()); existing .unique() changes require developer approval + handoff SQL only
MUST ask developer before changing drizzle schema
After schema edits: db:push per .ai/AI_SCHEMA_GUIDE.md — check .ai/dev-preferences.local.md; ask once, then remember
See .ai/AI_SCHEMA_GUIDE.md

3. Module scaffold (standard CRUD — when schema exists & module is new)

Read .ai/AI_MODULE_SCAFFOLD.md
From server/: bun run create:module {slug} --tag "..." then bun run create:page {group} {name} --tag "..."
Run in Agent mode when appropriate, or instruct user
If scaffold ran: skip hand-writing CRUD boilerplate — go to steps 5–8 for incremental work
If skipped: continue with step 4 as full backend generation

Read the full file on GitHub · 128 lines

Changes

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 · +3 lines e72898f21cc6
2mo ago First seen · 125 lines · 67 tokens per session scan A de86224a7ede

Subscribe to this mod's changes

elysia-module-dev is a skill published in the GitHub repository meishanlaoyao/elysia-admin (54 stars, last pushed 15d ago), licensed MIT. It adds 67 tokens to every session and 1,779 once invoked, about $0.0003 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-30.

Backend and APIs Databases

elysia-module-dev next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
elysia-module-devmeishanlaoyao/elysia-admin	Skill	54	15d ago	MIT	A	67	Cursor
event-store-designwshobson/agents	Skill	42k	yesterday	MIT	A	33	Claude Code
platform-custom-field-generateforcedotcom/sf-skills	Skill	1.1k	2d ago	Apache-2.0	A	139	Claude Code
field-service-sobject-create-configureforcedotcom/sf-skills	Skill	1.1k	2d ago	Apache-2.0	A	74	Claude Code
durable-objectsfcakyon/claude-codex-settings	Skill	1.2k	yesterday	Apache-2.0	A	22	Claude Code
nornicdb-grpcorneryd/NornicDB	Skill	923	today	MIT	A	98	Claude Code, Codex
nw-ddd-eventsourcingnWave-ai/nWave	Skill	631	yesterday	MIT	A	38	Claude Code

elysia-admin: Skill for Cursor