elysia-admin: Instructions file for Kiro

.kiro/steering/tech.md

elysia-admin tech.md is an instructions file for Kiro from meishanlaoyao/elysia-admin. It costs 353 tokens per session, scanned A, original, MIT.

Project instructions for an Elysia and Bun backend with a Vue 3 and TypeScript frontend. They define how parts of the application may depend on each other and how coding agents should make changes.

In plain words
What is it for?
Use them when adding or changing frontend pages, backend modules, data access, or generated code in this project.
Why use it?
They keep new code consistent with the existing structure and reduce accidental cross-module dependencies, unnecessary packages, and unrelated edits.

Instructions file for Kiro

Written for Kiro: installed under .kiro/.

This is meishanlaoyao/elysia-admin's own configuration. It tells Kiro how to work on elysia-admin itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything elysia-admin configures →

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/tech.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.

agentmods badge for elysia-admin tech.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/meishanlaoyao/elysia-admin/tech.svg)](https://agentmods.dev/instructions/meishanlaoyao/elysia-admin/tech)
Your own site
<a href="https://agentmods.dev/instructions/meishanlaoyao/elysia-admin/tech"><img src="https://agentmods.dev/badge/instructions/meishanlaoyao/elysia-admin/tech.svg" alt="Measured on agentmods" height="20"></a>
Per session 353 This file is loaded in full into every session.
When invoked 353 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00353 $0.00353
Opus 5 $0.00177 $0.00177
Sonnet 5 $0.00071 $0.00071
Haiku 4.5 $0.00035 $0.00035

Measured yesterday against content hash 5fe487c3dea9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

elysia-admin tech.md 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 yesterday.

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/tech.md · 48 lines

What it actually says

Tech Stack & Engineering Constraints

Stack

  • Frontend: Vue 3, TypeScript, Art Design Pro, Element Plus
  • Backend: Elysia, Bun; data access via repository + schema — no ad-hoc raw SQL in modules

Strict Dependency Direction

admin → server (HTTP only)

modules → core
modules → shared
modules → infrastructure

core  ✗→ modules
shared ✗→ modules
infrastructure ✗→ modules   (sandbox via worker-sandbox/, not infrastructure → modules)

shared ✗→ core/database       (cron + Redis lock: server/src/infrastructure/cron/cron-scheduler.ts)

Generation Principles

  1. Plan in ≤5 lines + file list before coding
  2. Minimal diff — no unrelated abstraction or refactors
  3. No new dependencies unless user asks
  4. Match existing patterns; ask before schema changes
  5. No over-engineering

Live references to .ai/ (do not duplicate long templates in steering)

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

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

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

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

  • Module workflow: AI_MODULE_WORKFLOW.md (prefer Skill checklist; full file only if ambiguous)
  • Code templates: AI_CODE_EXAMPLES_BACKEND.md / AI_CODE_EXAMPLES_FRONTEND.md (section only)
  • Page quality + quick ref: AI_PAGE_QUALITY.md, AI_CONTEXT_CAPSULE.md (on demand)
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.

  1. yesterday First seen · 48 lines · 353 tokens per session scan A 5fe487c3dea9

Subscribe to this mod's changes

elysia-admin tech.md is an instructions file published in the GitHub repository meishanlaoyao/elysia-admin (49 stars, last pushed 2d ago), licensed MIT. It adds 353 tokens to every session, about $0.0018 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.

Related

Other instructions, from other repositories

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,182 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

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

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens