fullstack-template: Instructions file for Codex

AGENTS.md

fullstack-template AGENTS.md is an instructions file for Codex, OpenCode from GRACENOBLE/fullstack-template. It costs 987 tokens per session, scanned A, original, MIT.

Project instructions for a full-stack application with a Go backend, Next.js web app, PostgreSQL database, and Android app. They describe setup commands, layer-specific guidance, and development workflows.

In plain words
What is it for?
They help set up the database and development servers, run the web and mobile projects, and follow the project’s test-driven development process.
Why use it?
They give contributors the repository’s expected tools, startup sequence, file-specific instructions, and testing rules before they change code.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions subagents; positional $N argument.

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

Reuse

Borrowing it

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

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 fullstack-template AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/gracenoble/fullstack-template/agents-md"><img src="https://agentmods.dev/badge/instructions/gracenoble/fullstack-template/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 987 This file is loaded in full into every session.
When invoked 987 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.00987 $0.00987
Opus 5.5 $0.00395 $0.00395
Sonnet 5.5 $0.00197 $0.00197
Haiku 4.5 $0.00099 $0.00099

Measured 1mo ago against content hash 83dbadae8dbe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fullstack-template 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 1mo 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

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 106 lines

How it starts

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

AGENTS.md

Fullstack project — Go + Gin backend, Next.js 16 + React 19 web app, PostgreSQL, Android mobile (Kotlin + Compose).

Each layer has its own AGENTS.md and docs/ folder. Read the file closest to what you are editing:

  • backend/AGENTS.md + backend/docs/ — Go API
  • web/AGENTS.md + web/docs/ — Next.js UI
  • mobile/AGENTS.md + mobile/docs/ — Android app

Claude Code users: see CLAUDE.md for the feature development workflow and subagent definitions.


Setup

Prerequisites: Go 1.21+, Node.js 20+, pnpm, Docker + Docker Compose, Android Studio Meerkat (2024.3+), JDK 17+, Android SDK API 36.

# 1. Database
cd backend && make docker-run

# 2. Backend API (hot reload, separate terminal)
cd backend && make watch        # → http://localhost:8080

# 3. Web app (separate terminal)
cd web && pnpm install && pnpm dev   # → http://localhost:3000

# 4. Mobile — open mobile/ in Android Studio and run on emulator/device
cd mobile && ./gradlew assembleDebug      # build only
cd mobile && ./gradlew installDebug       # build and install on connected device

Testing

TDD is required. Write failing tests first, then implement.

# Backend (Docker must be running)
cd backend && make test         # unit + integration
cd backend && make itest        # integration only

# Web
cd web && pnpm test             # Vitest unit + component tests
cd web && pnpm test:watch       # watch mode during development
cd web && pnpm lint
cd web && pnpm build

# Mobile
cd mobile && ./gradlew lint
cd mobile && ./gradlew test                  # unit tests (no device needed)
cd mobile && ./gradlew connectedAndroidTest  # instrumented tests (emulator/device required)
  • Backend DB and cache tests use Testcontainers (real PostgreSQL, real Redis). Never mock the database.
  • Web unit/component tests use Vitest + @testing-library/react. Server Component flows use Playwright (future).
  • Mobile Composable tests use Compose test rules in instrumented tests.

Read the full file on GitHub · 106 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. 1mo ago First seen · 106 lines · 987 tokens per session scan A 83dbadae8dbe

Subscribe to this mod's changes

fullstack-template AGENTS.md is an instructions file published in the GitHub repository GRACENOBLE/fullstack-template (6 stars, last pushed 1mo ago), licensed MIT. It adds 987 tokens to every session, about $0.0039 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-09-04.

Related

Other instructions, from other repositories