agentic-qa-boilerplate: Instructions file for Codex

AGENTS.md

agentic-qa-boilerplate AGENTS.md is an instructions file for Codex, OpenCode from upex-galaxy/agentic-qa-boilerplate. It costs 5,312 tokens per session, scanned A, original, MIT.

A set of persistent instructions for AI coding agents working on the agentic-qa-boilerplate repository, including rules for memory, planning, credentials, commits, and protected branches.

In plain words
What is it for?
Use it to guide test planning, implementation, reviews, credential handling, acceptance-criteria checks, and the project’s Git workflow.
Why use it?
It gives the agent consistent project rules across sessions and reduces mistakes such as hardcoding secrets, coding before planning, or pushing directly to protected branches.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

This is upex-galaxy/agentic-qa-boilerplate's own configuration. It tells Codex and OpenCode how to work on agentic-qa-boilerplate 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 agentic-qa-boilerplate configures →

Reuse

Borrowing it

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

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 agentic-qa-boilerplate AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/upex-galaxy/agentic-qa-boilerplate/agents-md"><img src="https://agentmods.dev/badge/instructions/upex-galaxy/agentic-qa-boilerplate/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 5,312 This file is loaded in full into every session.
When invoked 5,312 The same file — it is already loaded in full.
Security scan A 1 finding. 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.05312 $0.05312
Opus 5.5 $0.02125 $0.02125
Sonnet 5.5 $0.01062 $0.01062
Haiku 4.5 $0.00531 $0.00531

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

Security

Grade A, and why

agentic-qa-boilerplate AGENTS.md scanned grade A with 1 finding 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 16d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

1. **CREDENTIALS = BY NAME, NEVER BY VALUE**: Reference a secret only through its variable NAME (`$STAGING_USER_PASSWORD` expanded by the shell, `process.env.X` in code, a name in the MCP loader's `--filter` list). NEVER
AGENTS.md · 168 lines

How it starts

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

AGENTS.md: AI Persistent Memory

Always-on layer (L0). Detail lives in section files under .agents/instructions/, loaded through the ROUTER (progressive disclosure). Edit a section file, never paste section prose back here; project rules go in .agents/instructions/agent-project.md. Every instruction edit goes through /framework-development mode instructions.

LOAD PROTOCOL

Before acting on a request, match it against the ROUTER and read every matched section file not already in this conversation. A ROUTE: line injected by the hook is binding and wins over your own judgment: read its file before acting. A ROUTE-OPTIONAL: line is not binding: read one of its files only when the task needs it. A ROUTE-PENDING: line names a binding file still unread: read it before the next step. A section once read is not re-read unless compaction or /clear removed it. Unsure whether a section applies → read it: a skipped section is the failure this design guards against. A section binds exactly like this file. A §N citation anywhere names the numbered heading kept verbatim in the file the ROUTER lists for it.


1. CRITICAL RULES: ALWAYS APPLY

Each line is the rule's binding sentence; Full: agent-critical-rules.md#n = its full text in .agents/instructions/agent-critical-rules.md, under the heading ## n.

  1. CREDENTIALS = BY NAME, NEVER BY VALUE: Reference a secret only through its variable NAME ($STAGING_USER_PASSWORD expanded by the shell, process.env.X in code, a name in the MCP loader's --filter list). NEVER open, print or paste a secret value: no Read/cat/grep of .env* (except .env.example and the committed .env*.schema files), .auth/** or .claude/settings.local.json; no printenv, env, echo $SECRET, set -x, curl -v, varlock printenv|reveal, or varlock load without --agent. To learn WHETHER a variable is set, run the repo's redacted presence check (named in the full text). A missing secret value is the human's to type, in a terminal or the secret manager, never through the chat; the AI MAY write a non-sensitive value (URL, project key, flag, port) when asked. NEVER hardcode or guess. Full: agent-critical-rules.md#1
  2. PLAN BEFORE CODING: Produce test plan (spec.md / impl plan) BEFORE writing test code. Full: agent-critical-rules.md#2
  3. NO AI ATTRIBUTION: NEVER include "Generated with AI", harness branding, or AI Co-Authored-By trailers in commits. Forensic trailers are the one MANDATORY exception and are NOT attribution: every commit ends with Worktree: <name|primary> then Session: <label>. Full: agent-critical-rules.md#3
  4. SHIFT-LEFT: Evaluate ACs for clarity, testability, completeness. Full: agent-critical-rules.md#4
  5. PUSH TO PROTECTED = RESOLVE git_strategy.policy.direct_push_to_protected (.agents/project.yaml; protected list = git_strategy.protected): forbidden → NEVER direct-push, route through a PR. confirm → ask explicit user confirmation before EVERY push. allowed → standing authorization, push without asking. git_strategy block missing or null (fresh scaffold) → behave as confirm (safe default: ask). Full: agent-critical-rules.md#5
  6. GIT HISTORY (INVARIANTS, not strategy choices — no git_strategy value relaxes them): NEVER rewrite pushed history (rebase/amend on pushed commits). NEVER force-push a branch others may share. NEVER delete remote branches without confirmation. Full: agent-critical-rules.md#6
  7. QUALITY VERIFICATION: After code changes, verify in order: tests → types → lint. Full: agent-critical-rules.md#7
  8. FILE OPERATIONS: ALWAYS read file before edit. Preserve formatting + indent. NEVER overwrite without reading. Full: agent-critical-rules.md#8
  9. SKILLS-FIRST: All workflows live in .agents/skills/. NEVER paste instructions inline. Full: agent-critical-rules.md#9
  10. MCP CREDENTIAL FAILURE = STOP IMMEDIATELY: NO workaround. STOP, tell user exact env var, point to .env / .env.example, ask fix .env + RESTART AGENT SESSION (env cached at MCP-spawn time, no refresh mid-session). MCP UNAVAILABLE = SAME STOP, AT THE POINT OF USE. Full: agent-critical-rules.md#10
  11. SCRIPTS = READ package.json DIRECTLY. NEVER quote test/build commands from this file or any doc: drift kills. Full: agent-critical-rules.md#11
  12. KATA MANIFEST = SOURCE OF TRUTH. Before proposing new Page, Api, Steps module, or @atc('PROJ-XXX') ID: MUST load kata-manifest.json and check it. Full: agent-critical-rules.md#12
  13. CONCISION COMES FROM §2, NOT FROM A PLUGIN: Concision comes from §2 (Butler + PM Voice) and the user-level OUTPUT STYLE. No communication-mode plugin is assumed or recommended. Full: agent-critical-rules.md#13
  14. LANGUAGE DETECTION + MIRRORING: Mirror that language in ALL conversational replies (questions, summaries, explanations, status updates). Repo artifacts ALWAYS English regardless of conversation language. Full: agent-critical-rules.md#14
  15. NO GLOBAL DISCARDS (MULTI-SESSION SAFETY): PROHIBITED to run repo-wide destructive git commands: git restore ., git checkout -- ., git reset --hard, untargeted git stash, git clean -f. Discard ONLY explicit paths YOU modified in THIS session. Full: agent-critical-rules.md#15
  16. A SUCCESS CODE DESCRIBES THE CALL, NEVER THE OUTCOME — VERIFY AT THE DESTINATION: a write is verified by READING IT BACK from the destination, a message by the recipient answering it, a transition by re-reading the issue's status, a file write by re-parsing the file, a dispatch by the worker's own first report. Full: agent-critical-rules.md#16
  17. COMMITTED PROSE NAMES THE SOURCE OF TRUTH, NEVER ITS CURRENT VALUE: text that is committed (this file, .agents/**, docs/**, README.md, INSTALLER.md, .env.example, the decks) NEVER states a fact that changes with the normal life of the repo or the tracker. Full: agent-critical-rules.md#17

Read the full file on GitHub · 168 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. 16d ago Changed · +2 lines · +1 tokens per session ce47f61da849
  2. 17d ago Changed · +9 lines · +843 tokens per session 0298ceff34c5
  3. 18d ago Changed · -469 lines · -23,773 tokens per session scan D → A 51c742ce523f
  4. 20d ago Changed · +8 lines · +985 tokens per session scan C → D 89e34a675847
  5. 21d ago Changed · +294 tokens per session 9bd886d81697
  6. 22d ago Changed · +7 lines · +1,405 tokens per session 3fc2c7e86141
  7. 27d ago Changed · -19 lines · +160 tokens per session 9d5605239858
  8. 28d ago Changed · +7 lines · +1,478 tokens per session faba6b72fa6a
  9. 29d ago Changed · +15 tokens per session 97f28ee82d80
  10. 1mo ago First seen · 623 lines · 23,904 tokens per session scan C 10a49a67dc10

Subscribe to this mod's changes

agentic-qa-boilerplate AGENTS.md is an instructions file published in the GitHub repository upex-galaxy/agentic-qa-boilerplate (26 stars, last pushed 11d ago), licensed MIT. It adds 5,312 tokens to every session, about $0.0212 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

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,649 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,549 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

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens