What is ai-ops-supplement?

A set of instructions for building and maintaining modules in an Elysia Admin application. It covers database checks, CRUD screens, permissions, shared value lists, handoff SQL, and frontend page quality.

Use it when creating CRUD modules and pages, checking PostgreSQL data through a read-only connection, aligning menus and permissions, and preparing initialization SQL.

It reduces inconsistency when adding an application module by putting the database, server, interface, permissions, and handoff steps in one workflow.

How meishanlaoyao/elysia-admin configures Kiro

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/.kiro/steering/ai-ops-supplement.md

Clone the repo

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

Made for: Kiro.

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/instructions/meishanlaoyao/elysia-admin/ai-ops-supplement/github.svg)](https://agentmods.dev/instructions/meishanlaoyao/elysia-admin/ai-ops-supplement)

Your own site

<a href="https://agentmods.dev/instructions/meishanlaoyao/elysia-admin/ai-ops-supplement"><img src="https://agentmods.dev/badge/instructions/meishanlaoyao/elysia-admin/ai-ops-supplement/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/instructions/meishanlaoyao/elysia-admin/ai-ops-supplement"><img src="https://agentmods.dev/badge/instructions/meishanlaoyao/elysia-admin/ai-ops-supplement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 594 This file is loaded in full into every session.

When invoked 594 The same file — it is already loaded in full.

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

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.00594	$0.00594
Opus 5	$0.00297	$0.00297
Sonnet 5	$0.00119	$0.00119
Haiku 4.5	$0.00059	$0.00059

Measured 4d ago against content hash ff96ace3e13d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

ai-ops-supplement 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 4d 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.

.kiro/steering/ai-ops-supplement.md · 37 lines

What it actually says

AI Ops & Module Workflow (summary)

Full SOP:

#[[file:.ai/AI_MODULE_WORKFLOW.md]]

Scaffold (CRUD boilerplate): #[[file:.ai/AI_MODULE_SCAFFOLD.md]]

Sub-guides:

Page quality: #[[file:.ai/AI_PAGE_QUALITY.md]]
Schema: #[[file:.ai/AI_SCHEMA_GUIDE.md]]
Handoff SQL: #[[file:.ai/AI_HANDOFF_SQL.md]]
MCP: #[[file:.ai/AI_MCP_SETUP.md]]
Form layout: #[[file:.ai/AI_UI_LAYOUT.md]]
Quick ref: #[[file:.ai/AI_CONTEXT_CAPSULE.md]]

Key points

Flow: check server/database/schema/ → scaffold (create:module + create:page from server/) → dict (no hardcoded enums; short semantic dict_type e.g. goods_status; skip dict for pure boolean — .ai/AI_HANDOFF_SQL.md) → frontend polish → single SQL at server/database/sql/{module}-init.sql
Rule-file language: when editing English AI rule docs, write new/changed prose in English (this edit only — no bulk translate)
Postgres MCP: read-only for tables/dict/menu IDs; MUST prefer MCP over pg.sql; never DDL/write via MCP
NEVER read or modify server/database/sql/pg.sql — backup snapshot only; may not match live DB
Soft delete & uniqueness: uniqueness checks include soft-deleted rows; new unique → partial index WHERE del_flag = false
Form validation both sides: frontend rules + backend dto.ts; entity dropdowns → cached /options (not /list)
handle.ts JSDoc: every exported function needs purpose + @param / @returns
db:push: after schema edits, check .ai/dev-preferences.local.md; ask once, then remember — see .ai/AI_SCHEMA_GUIDE.md
Handoff SQL: generate file only; developer runs manually; NEVER ad-hoc scripts/MCP execute
Menu SQL: query live DB before INSERT; permissions match route.ts and frontend auth
Page quality: art-full-height, useDictStore, see AI_PAGE_QUALITY.md
Git: AI read-only — no add/commit/push

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.

4d ago First seen · 37 lines · 594 tokens per session scan A ff96ace3e13d

Subscribe to this mod's changes

ai-ops-supplement is an instructions file published in the GitHub repository meishanlaoyao/elysia-admin (49 stars, last pushed 2d ago), licensed MIT. It adds 594 tokens to every session, about $0.0030 per session on Opus 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-09-06.

Backend and APIs Databases PostgreSQL

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

elysia-admin: Instructions file for Kiro