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/frontend)<a href="https://agentmods.dev/rules/meishanlaoyao/elysia-admin/frontend"><img src="https://agentmods.dev/badge/rules/meishanlaoyao/elysia-admin/frontend.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.02487 |
| Opus 5 | $0.00000 | $0.01243 |
| Sonnet 5 | $0.00000 | $0.00497 |
| Haiku 4.5 | $0.00000 | $0.00249 |
Grade A, and why
frontend 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.
How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend File Structure
admin/src/
types/api/{group}-{name}.d.ts ← type declarations (declare namespace Api)
api/{group}/{name}.ts ← HTTP wrappers only
views/{group}/{name}/
index.vue ← page container (useTable, columns, dialog control)
modules/
{name}-search.vue ← search form only
{name}-dialog.vue ← add/edit form only
Type Declaration Pattern (types/api/)
declare namespace Api {
namespace GroupName { // PascalCase group + module name
interface NameListItem {
nameId?: number;
fieldA?: string;
status?: boolean;
createTime?: Date;
// ... mirror backend schema fields
}
type NameList = Api.Common.PaginatedResponse<NameListItem>
type NameSearchParams = Partial<
Pick<NameListItem, 'fieldA' | 'status'> &
Api.Common.CommonSearchParams
>
}
}
API Layer Pattern (api/{group}/{name}.ts)
import request from '@/utils/http'
// Naming: fetch + Action + ModuleName
export function fetchCreateName(data: Api.GroupName.NameListItem) {
return request.post({ url: '/api/group/name', data, showSuccessMessage: true, showErrorMessage: true })
}
export function fetchGetNameList(params: Api.GroupName.NameSearchParams) {
return request.get<Api.GroupName.NameList>({ url: '/api/group/name/list', params })
}
export function fetchGetNameDetail(id: number) {
return request.get<Api.GroupName.NameListItem>({ url: `/api/group/name/${id}` })
}
export function fetchUpdateName(data: Api.GroupName.NameListItem) {
return request.put({ url: '/api/group/name', data, showSuccessMessage: true, showErrorMessage: true })
}
export function fetchDeleteName(ids: number | string) {
return request.delete({ url: `/api/group/name/${ids}`, showSuccessMessage: true, showErrorMessage: true })
}
useTable Pattern (index.vue script)
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 · 249 lines · 0 tokens per session scan A ddb52fb691f9
frontend is a cursor rule published in the GitHub repository meishanlaoyao/elysia-admin (49 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,487 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
svelte-5-vs-svelte-4-cursorrules-prompt-file
Cursor rules for comparing Svelte 5 and Svelte 4 development.
sveltekit-typescript-guide-cursorrules-prompt-file
Cursor rules for SvelteKit development with TypeScript integration.
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
svelte-mcp-tools
Instructions for using the Svelte MCP server tools for documentation lookup, code analysis, and validation.
frontend-component
Vue component structure, styling, derived state, modals, icons, DaisyUI/Tailwind frontend component conventions.
frontend
Vue frontend — components, Vitest, generated API client, apiCallWithLoading, DaisyUI. Read this first for any frontend work.