agentic-qa-boilerplate: Instructions file for Claude Code

AGENTS.md

agentic-qa-boilerplate AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from upex-galaxy/agentic-qa-boilerplate. It costs 18,624 tokens per session, scanned B, 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 Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: $ARGUMENTS substitution, but also reads ~/.codex or $CODEX_HOME. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is upex-galaxy/agentic-qa-boilerplate's own configuration. It tells Claude Code, 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: Claude Code, 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.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.svg" alt="Measured on agentmods" height="20"></a>
Per session 18,624 This file is loaded in full into every session.
When invoked 18,624 The same file — it is already loaded in full.
Security scan B 2 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.18624 $0.18624
Opus 5 $0.09312 $0.09312
Sonnet 5 $0.03725 $0.03725
Haiku 4.5 $0.01862 $0.01862

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

Security

Grade B, and why

agentic-qa-boilerplate AGENTS.md scanned grade B with 2 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 2d 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.

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

**MCP: one declared set, three formats, semantic parity.** The canonical server set is whatever `.mcp.json` declares: every server there must exist in `opencode.jsonc` and `.codex/config.toml` with the same `.env` depend

Makes network callslowCapability

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

| OpenAPI | API **schema** read-only (endpoint discovery, request/response contracts) | `[API_TOOL]` schema-read leg ONLY. Authenticated execution is `curl`, NOT the MCP: see `agentic-qa-core/references/api-testing-doctr
AGENTS.md · 580 lines

How it starts

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

AGENTS.md: AI Persistent Memory

AI memory. Loads EVERY session. Heavy detail → skill references/. Project values → .agents/project.yaml. Scripts → READ package.json. User-facing setup → README.md / docs/.


1. CRITICAL RULES: ALWAYS APPLY

  1. CREDENTIALS: ALWAYS read from .env. NEVER hardcode/guess. Example keys: LOCAL_USER_EMAIL, STAGING_USER_PASSWORD.
  2. PLAN BEFORE CODING: Produce test plan (spec.md / impl plan) BEFORE writing test code. Flow: Plan → Code → Review.
  3. NO AI ATTRIBUTION: NEVER include "Generated with AI", harness branding, or AI Co-Authored-By trailers in commits. Commits look human-authored.
  4. SHIFT-LEFT: Evaluate ACs for clarity, testability, completeness. Raise questions ONLY when genuine gaps exist, never force questions to fill checklist.
  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). NEVER hardcode the answer here — the variable is the decision.
  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 — at minimum every branch in git_strategy.protected, plus integration/ephemeral trunks in git_strategy.branches. NEVER delete remote branches without confirmation. ALWAYS add forward (new commits, not rewrite). ALWAYS preserve merge history.
  7. QUALITY VERIFICATION: After code changes, verify in order: tests → types → lint. No skip steps.
  8. FILE OPERATIONS: ALWAYS read file before edit. Preserve formatting + indent. NEVER overwrite without reading.
  9. SKILLS-FIRST: All workflows live in .agents/skills/. NEVER paste instructions inline. Invoke matching skill, let it self-load detail. Use [TAG_TOOL] pseudocode + {{VARIABLES}} for dynamic content.
  10. MCP CREDENTIAL FAILURE = STOP IMMEDIATELY: MCP fail auth or env var missing (.mcp.json use ${VAR}: Claude Code fail parse if unset; opencode.jsonc use {env:VAR}: OpenCode silently substitute empty → 401/403 is signal). 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).
  11. SCRIPTS = READ package.json DIRECTLY. NEVER quote test/build commands from this file or any doc: drift kills. Open package.json first, then answer.
  12. KATA MANIFEST = SOURCE OF TRUTH. kata-manifest.json (root) is authoritative registry of every existing Component + ATC. Before proposing new Page, Api, Steps module, or @atc('PROJ-XXX') ID: MUST load kata-manifest.json and check it. Anti-duplication gate. Stale manifest blocks commits via .husky/pre-commit. Regenerate: bun run kata:manifest. Validate: bun run kata:manifest:check.
  13. DEFAULT COMMUNICATION MODE: CAVEMAN: If caveman skill installed user-level (~/.claude/skills/caveman/), respond caveman level full by default (drop articles, fillers, pleasantries; fragments OK; technical terms exact; code/commits/PRs/security warnings always write normal English: caveman built-in boundary). Revert verbose ONLY when user explicitly say "normal mode", "habla normal", "stop caveman", "speak normally", "be verbose", "más detallado" or clear semantic equivalent. If caveman skill not installed, rule = no-op.
  14. LANGUAGE DETECTION + MIRRORING: At start of every conversation, READ FULL USER MESSAGE (not just opening words) to detect user's working language. Mirror that language in ALL conversational replies (questions, summaries, explanations, status updates). Repo artifacts ALWAYS English regardless of conversation language: code, code comments, commits, PR titles + bodies, branch names, file names, test names, configuration values, + any external action artifact (Jira issues/comments, GitHub issues/PRs/comments, Slack messages, emails, deploy notes, MCP tool inputs). Override: if user explicitly request another language for specific artifact ("crea el ticket en español", "write this PR description in Spanish"), honor that request only for that artifact + continue defaulting to English for next ones unless re-requested.
  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. Multiple agent sessions may share this working tree without worktrees: a global discard silently destroys another session's uncommitted work, unrecoverably. Discard ONLY explicit paths YOU modified in THIS session (git restore <path>... / git stash push <path>...). Unsure who modified a file → do NOT restore it: ask the user.

Read the full file on GitHub · 580 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. 2d ago Changed · +3 lines · +1,747 tokens per session scan A → B bb75474d6030
  2. 3d ago Changed · +7 lines · +664 tokens per session f92abc126821
  3. 7d ago First seen · 570 lines · 16,213 tokens per session scan A d5e35093ec4f

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 (21 stars, last pushed 2d ago), licensed MIT. It adds 18,624 tokens to every session, about $0.0931 per session on Opus 5. A static security scan graded it B with 2 findings (reads mcp configuration, 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

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.

openai/codex · 5,182 tokens

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 · 6,785 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,296 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,469 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens