LiteStack: Instructions file for Codex

AGENTS.md

LiteStack AGENTS.md is an instructions file for Codex, OpenCode from uxname/LiteStack. It costs 1,225 tokens per session, scanned A, original, MIT.

Project instructions for LiteStack, a full-stack boilerplate that combines separate frontend and backend projects. They explain which project should contain each kind of change.

In plain words
What is it for?
Use them when changing server code, browser code, shared project coordination, or the way the frontend and backend connect.
Why use it?
They prevent application code from going into the wrong project and guide agents to the relevant instructions before editing.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents; mentions AGENTS.md.

This is uxname/LiteStack's own configuration. It tells Codex and OpenCode how to work on LiteStack 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 LiteStack configures →

Reuse

Borrowing it

Nothing to install: this file belongs to uxname/LiteStack. 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/uxname/LiteStack/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/uxname/LiteStack

Made for: Codex, OpenCode.

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 LiteStack AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/uxname/litestack/agents-md/github.svg)](https://agentmods.dev/instructions/uxname/litestack/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/uxname/litestack/agents-md"><img src="https://agentmods.dev/badge/instructions/uxname/litestack/agents-md/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.

agentmods 80×15 button for LiteStack AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/uxname/litestack/agents-md"><img src="https://agentmods.dev/badge/instructions/uxname/litestack/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,225 This file is loaded in full into every session.
When invoked 1,225 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.01225 $0.01225
Opus 5.5 $0.00490 $0.00490
Sonnet 5.5 $0.00245 $0.00245
Haiku 4.5 $0.00122 $0.00122

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

Security

Grade A, and why

LiteStack 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 8d 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.

AGENTS.md · 63 lines

How it starts

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

AGENTS.md — LiteStack (meta-repo)

LiteStack is a full-stack boilerplate: two projects as git submodules — backend/ (liteend-go) and frontend/ (litefront), each its own repo — plus this thin layer that only coordinates them. The product's requirements live here in docs/src (docc), and a clickable prototype, protokit/, is a third submodule until a product removes it; both are tied to the code by docc: tags (ADR-0011). Application code always lives in a submodule: a resolver, a component or a migration at this root means you are in the wrong folder.

Every task

  1. Lessons first. If docs/retro/ holds dated files, read their "Rule" lines before touching code (how).
  2. Go to the box that owns the change (table below) and read that sub-project's AGENTS.md; it routes on to its .agents/*.md. Inside a sub-project, its rules win over this file.
  3. Write to the standard. Code, tests, log lines and commit messages follow .agents/CODING_STANDARDS.md. Everything committed is English, whatever language the chat is in.
  4. A structural decision gets an ADR the same session, before the code lands — criteria in docs/adr/README.md. Before changing an area, read the ADRs that cover it.
  5. Done means the gate is green by exit status, never by the tail of its output: task check in backend/, npm run check in frontend/, the hook in lefthook.yml here. There is no CI (ADR-0001): the hooks are the only gate, so every commit and push runs them in full — --no-verify skips the whole guarantee.

Where to go

Your task Go to
API, database, business logic, jobs, server-side GraphQL backend/AGENTS.md
UI, routing, client state, styling, GraphQL the browser sends frontend/AGENTS.md
What the product must do: read or change a requirement — every edit reaches the prototype and the code tagged with it docs/src, the docc skill; the rules in .agents/CROSS-PROJECT.md → "Requirements"
The prototype: a screen or a path on the simulated server protokit/, the protokit skill; removing it: .agents/OPERATING-MODE.md
A feature on both sides requirement first, then the prototype (while there is one), then backend — the full-stack-feature skill
A back ↔ front seam (codegen, auth audience, CORS + WebSockets, requestId), or who owns a shared value .agents/CROSS-PROJECT.md
An env var both sides must agree on docs/ENV-CONTRACT.md
Commit or push: template vs derived mode decides the remote the commit skill; rules in .agents/OPERATING-MODE.md
Derive a real product from the template .agents/DERIVE.md
A change to boundaries, protocols or components — the architecture model moves in the same change docs/architecture/likec4/ (ADR-0003)
Deploy: local Docker, Dokploy, registry images docs/DEPLOY.md
Observability: errors, logs, metrics, traces, product analytics, alerts — deploy the shared stack, connect a project, read its data docs/observability/
First-time setup of a clone, toolchain README.md → "Getting started"
See what the frontend does at runtime (you have no browser) frontend/.agents/OBSERVABILITY.md
Triage a failure from the logs backend/docs/DEBUGGING.md, then the row above
Team process, or adding agent guidance or a skill docs/TEAM.md

Read the full file on GitHub · 63 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.

  1. 8d ago Changed · +6 lines · +207 tokens per session fd56ec9933d8
  2. 27d ago Changed · +1 lines · +49 tokens per session ab7dc8b947e7
  3. 29d ago Changed · -60 lines · -857 tokens per session b72d28f0a389
  4. 1mo ago Changed · -14 lines · -177 tokens per session fe8dda17da95
  5. 2mo ago Changed · +1 lines · +20 tokens per session d60946fa7068
  6. 2mo ago Changed · +1 lines · +12 tokens per session 4ae4273953ef
  7. 2mo ago Changed · +18 lines · +429 tokens per session a98f5cbb939e
  8. 2mo ago Changed · -36 lines · -727 tokens per session 0b4f6ed622cd
  9. 2mo ago First seen · 146 lines · 2,269 tokens per session scan A 2f1d2bf81248

Subscribe to this mod's changes

LiteStack AGENTS.md is an instructions file published in the GitHub repository uxname/LiteStack (2 stars, last pushed 5d ago), licensed MIT. It adds 1,225 tokens to every session, about $0.0049 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-31.

Related

LiteStack AGENTS.md compared with instructions from other repositories

LiteStack AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
LiteStack AGENTS.mduxname/LiteStackInstructions file25d agoMITA1,225Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode