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.
npx agentmods add instructions/wang-baohai/omni-stack/agents-mdgit clone --depth 1 https://github.com/wang-baohai/Omni-StackWhat 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 | $0.09611 | $0.09611 |
| Opus 5 | $0.04806 | $0.04806 |
| Sonnet 5 | $0.01922 | $0.01922 |
| Haiku 4.5 | $0.00961 | $0.00961 |
Grade A, and why
Omni-Stack AGENTS.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 3d 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 — 506 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project Identity
Omni-Stack is a microservices scaffolding platform built with Spring Boot 4 + Vue 3, organized as a monorepo with a Maven multi-module backend and a standalone npm frontend.
| Layer | Technology | Version |
|---|---|---|
| JDK | OpenJDK | 25 |
| Backend | Spring Boot | 4.0.6 |
| Cloud | Spring Cloud | 2025.1.1 |
| Cloud Alibaba | Spring Cloud Alibaba | 2025.1.0.0 |
| Gateway | Spring Cloud Gateway Server (WebFlux) | 5.0.1 |
| Service Discovery / Config | Nacos Server | v3.1.1 |
| Circuit Breaker / Flow Control | Spring Cloud Alibaba Sentinel client | 2025.1.0.0 (Dashboard optional) |
| Frontend | Vue 3 + TypeScript | 3.5.35 / 5.9.3 |
| Bundler | Vite 8 (Rolldown) | 8.2.1 |
| UI Framework | Element Plus | 2.14.0 |
| State | Pinia | 3.0.4 |
| Router | Vue Router | 5.0.7 |
| Node.js | Node.js LTS | >= 22.12.0 |
System Truth
Architecture, patterns, API contracts, and core flows are documented in docs/. Read those first. This file contains only execution rules and build commands.
| Document | Purpose |
|---|---|
docs/architecture.md |
System boundaries, module map, data flow, RBAC permission system, constraints |
docs/api-contract.md |
Response format, error codes, pagination, naming |
docs/backend-patterns.md |
Java layering, validation, exceptions, logging, security & data permission, OOP rules |
docs/frontend-patterns.md |
Vue/TS patterns, state management, routing, permission control, component conventions |
docs/core-flows.md |
End-to-end traces of login (password + captcha, GitHub social, Gitee social, device code), RBAC functional permission (Flow 5), data permission (Flow 6), XSS defense (Flow 8) |
docs/scheduling.md |
Scheduled task system: dual-track architecture (system tasks + user tasks), XXL-JOB integration, creating new task types |
docs/workflow.md |
Workflow engine: Flowable integration, dual-version model management, multi-instance countersign, candidate resolution, approval flows |
docs/crm.md |
CRM sales pipeline: domain model, 6-layer security, state machine, lead conversion, extension guide |
docs/design/srm-design.md |
SRM MVP: supplier lifecycle, portal Saga, evaluation/risk, data scope, API and deployment constraints |
docs/design/procurement-design.md |
Procurement: material catalog, requisition approval, RFQ/quotation, purchase order and goods receipt boundaries |
docs/design/asset-design.md |
Asset MVP: asset ledger, procurement receipt ingestion, allocation/return, transfer/disposal approval and data scope |
docs/mq-reliability.md |
Reliable message sending: Transactional Outbox pattern, status machine, retry strategy, tenant isolation, new service onboarding |
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.
- 3d ago First seen · 506 lines · 9,611 tokens per session scan A f8adf53411be
Omni-Stack AGENTS.md is an instructions file published in the GitHub repository wang-baohai/Omni-Stack (91 stars, last pushed 16d ago), licensed Apache-2.0. It adds 9,611 tokens to every session, about $0.0481 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-08-30.
Other instructions, from other repositories
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.