What is agent-template AGENTS.md?

Repository instructions for a home-operations GitOps project. GitOps means managing infrastructure by storing its desired configuration in version control; this project uses it to manage a three-node Talos Linux Kubernetes cluster.

Use them when changing Kubernetes applications, Flux configuration, networking, storage, backups, monitoring, or related cluster setup.

They tell coding agents where the cluster configuration lives, which tools and services it uses, and which narrower instructions apply to different areas.

How Zwanan-github/agent-template configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to Zwanan-github/agent-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/Zwanan-github/agent-template/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/Zwanan-github/agent-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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/zwanan-github/agent-template/agents-md/github.svg)](https://agentmods.dev/instructions/zwanan-github/agent-template/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/zwanan-github/agent-template/agents-md"><img src="https://agentmods.dev/badge/instructions/zwanan-github/agent-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/zwanan-github/agent-template/agents-md"><img src="https://agentmods.dev/badge/instructions/zwanan-github/agent-template/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 4,199 This file is loaded in full into every session.

When invoked 4,199 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.

Model	Per session	Once invoked
Fable 5.1	$0.04199	$0.04199
Opus 5.5	$0.01680	$0.01680
Sonnet 5.5	$0.00840	$0.00840
Haiku 4.5	$0.00420	$0.00420

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

Security

Grade A, and why

agent-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 2mo 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 · 536 lines

How it starts

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

AGENTS.md

Purpose

This project uses written specs to keep feature work clear, reviewable, and resumable.

Do not rely only on chat history for feature context. Any feature that may span multiple steps, files, or sessions must have its current state saved under specs/features/. Complex, large, unclear, research-heavy, or architecture-heavy work should also save upstream design context under specs/docs/.

Scope

These instructions apply to the entire repository unless a more specific AGENTS.md exists in a subdirectory.

User instructions in the current conversation take priority over this file.

Spec Directory

Feature and Epic specs are stored in:

specs/features/

Design and reference documents are stored under:

specs/docs/

Use this filename format:

YYYY-MM-DD-short-feature-name.md

For large requirements that coordinate multiple child feature specs, use an Epic spec with an -epic suffix when practical:

YYYY-MM-DD-short-epic-name-epic.md

Examples:

2026-05-22-user-login-flow.md 2026-05-22-export-csv.md 2026-05-22-payment-retry-policy.md 2026-05-22-import-workflow-epic.md

Use lowercase words separated by hyphens. Keep names short but recognizable.

Design docs use the same date-prefixed lowercase hyphen format under type-specific directories, for example:

specs/docs/research/2026-05-22-payment-provider-research.md specs/docs/product/2026-05-22-import-workflow-mvp.md specs/docs/architecture/2026-05-22-import-workflow-solution.md specs/docs/design/2026-05-22-import-review-flow.md specs/docs/decisions/2026-05-22-use-background-import-worker.md

Use specs/docs/ for upstream context and specs/features/ for executable feature/Epic specs, progress, tests, and resume notes.

Agent Workflow Assets

Reusable agent workflow assets are grouped under agent-workflow/:

agent-workflow/guides/      # tutorials, evaluation guide, and tool-specific notes
agent-workflow/skills/      # reusable workflow prompts for common agent tasks
agent-workflow/templates/   # reusable markdown templates

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

2mo ago First seen · 536 lines · 4,199 tokens per session scan A ad24d0d5ac7f

Subscribe to this mod's changes

agent-template AGENTS.md is an instructions file published in the GitHub repository Zwanan-github/agent-template (2 stars, last pushed 3mo ago), licensed MIT. It adds 4,199 tokens to every session, about $0.0168 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.

DevOps and cloud agentic-workflow harness harness-engineering

agent-template AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
agent-template AGENTS.mdZwanan-github/agent-template	Instructions file	2	3mo ago	MIT	A	4,199	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

agent-template: Instructions file for Codex