livestore: Instructions file for Codex

AGENTS.md

livestore AGENTS.md is an instructions file for Codex, OpenCode from livestorejs/livestore. It costs 1,553 tokens per session, scanned A, a copy of superpowers AGENTS.md, Apache-2.0.

Repository instructions for LiveStore, a state-management framework that uses SQLite and synchronizes data between users or devices. They give a coding agent project-specific guidance to follow.

In plain words
What is it for?
Use them when changing the LiveStore codebase so the agent follows its documented project rules.
Why use it?
They reduce mistakes caused by an agent not knowing the project's structure, conventions, or data-synchronization rules.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

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

About the project

LiveStore is a state-management framework that stores application data in SQLite, a database embedded in the application, and synchronizes that data through a built-in engine. It is intended for applications that keep data locally while supporting reactive updates and synchronization.

livestorejs/livestore · 3,740 stars · on GitHub · livestore.dev

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/livestorejs/livestore/agents-md"><img src="https://agentmods.dev/badge/instructions/livestorejs/livestore/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,553 This file is loaded in full into every session.
When invoked 1,553 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 100% copy Near-identical to another mod 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.01553 $0.01553
Opus 5.5 $0.00621 $0.00621
Sonnet 5.5 $0.00311 $0.00311
Haiku 4.5 $0.00155 $0.00155

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

Security

Grade A, and why

livestore 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 29d 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.

Origin

This is a copy

100% identical to superpowers AGENTS.md — 165 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 123 lines

How it starts

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

Project-Specific Instructions for Coding Agents

Setup

Minimal Setup

For ordinary TypeScript, core unit-test, Vite, local Wrangler, and docs-check work, provide Node.js 24, Bun, and the exact pnpm version declared by package.json#packageManager, then run:

./scripts/bootstrap-minimal.sh

The script verifies prerequisites and performs a frozen install; it never installs tools globally. Bun 1.3.13 is the known-good Docker realization. The optional root compose.yaml supplies that toolchain in an exclusive bind-mounted checkout.

Full Setup (Nix + devenv)

Run devenv shell for Playwright and full docs builds, generated-source or wa-sqlite changes, release and infrastructure work, or repository-wide parity. Before final handoff, escalate to this lane whenever the relevant validation extends beyond the finite Minimal Setup checks; setup success never substitutes for the full required CI bar. The authoritative boundary is context/03-delivery/01-composition/01-developer-environment/spec.md.

Intent Layer (context/)

context/ is the project's intent layer (a VRS tree) — the always-current source of truth for the system's design: vision, requirements, subsystem contracts (spec.md), ontology, decisions, and tracked drift. Read context/spec.md for its structure and conventions (branch layout, ID scheme, maturity markers, enforcement).

  • When you change system behavior or a contract, update the owning context/ node. The docs site (docs/) derives from the intent layer and must not contradict it; context/ontology.md is the canonical source for terms.
  • Consequential choices → the node's .decisions/; confirmed divergence between intent and code → its .delta/; open design questions → open-questions.md. New/unaccepted proposals live in contributor-docs/rfcs/, not in spec bodies — they fold into the owning nodes on acceptance.
  • vision.md and requirements.md are protected — confirm with a maintainer before editing them; specs, decisions, deltas, and open questions evolve freely.
  • A Vitest suite (tests/package-common/src/intent-layer/) checks the tree's mechanical invariants (ID uniqueness, refines: resolution, links, decision shape, …); run it and keep it green when editing context/.

Read the full file on GitHub · 123 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. 29d ago Changed · +122 lines · +1,549 tokens per session 5adbc08c7a74
  2. 1mo ago First seen · 1 lines · 4 tokens per session scan A 6ebdb617a810

Subscribe to this mod's changes

livestore AGENTS.md is an instructions file published in the GitHub repository livestorejs/livestore (3,740 stars, last pushed 6d ago), licensed Apache-2.0. It adds 1,553 tokens to every session, about $0.0062 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to superpowers AGENTS.md, differing in 165 lines, and is treated as a copy.

Related

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).

microsoft/vscode · 9,715 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,581 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens