awesome-go: Instructions file for Codex

AGENTS.md

awesome-go AGENTS.md is an instructions file for Codex, OpenCode from avelino/awesome-go. It costs 774 tokens per session, scanned A, original, MIT.

A contribution guide for Awesome Go, a curated list of Go resources with a generated website.

In plain words
What is it for?
Use it when editing the resource list, its Go site generator, templates, or related tests and automation.
Why use it?
It explains how to add or change list entries while preserving the project's ordering, quality, and neutral writing style.

Instructions file for CodexOpenCode

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

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

About the project

Awesome Go is a curated directory of frameworks, libraries, and other software written for the Go programming language. Go developers use it to discover tools and projects, and contributors improve the list by submitting changes.

avelino/awesome-go · 190,881 stars · on GitHub · awesome-go.com

Reuse

Borrowing it

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

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 awesome-go AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/avelino/awesome-go/agents-md"><img src="https://agentmods.dev/badge/instructions/avelino/awesome-go/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 774 This file is loaded in full into every session.
When invoked 774 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.00774 $0.00774
Opus 5.5 $0.00310 $0.00310
Sonnet 5.5 $0.00155 $0.00155
Haiku 4.5 $0.00077 $0.00077

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

Security

Grade A, and why

awesome-go 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 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.

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 · 54 lines

How it starts

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

awesome-go · LLM Contribution Guide

This document summarizes the project context and the conventions that language models must follow when helping on this repository.

Project Snapshot

  • Purpose: maintain the curated README.md list of Go resources and generate the static site via go run ..
  • Primary language: Go 1.26 (go 1.26.0 in go.mod, toolchain go1.27.3). Supporting JavaScript exists only for the GitHub Action in .github/scripts.
  • Key entry points:
    • main.go: reads README.md, builds category pages, and writes artifacts to out/ using templates in tmpl/.
    • pkg/markdown and pkg/slug: helper packages used by the generator.
    • .github/workflows/: CI pipelines for PR quality validation, stale checks, site deployment, and Go tests.

When Modifying the Awesome List

  • Read and respect CONTRIBUTING.md (alphabetical order, one item per PR, descriptions end with a period, etc.).
  • Keep categories with at least three entries and verify surrounding entries still meet quality standards.
  • Avoid promotional copy; descriptions must stay concise and neutral.
  • Do not drop existing content unless removal is requested and justified.

Coding Guidelines

  • Go:
    • Use standard formatting (gofmt) and idiomatic Go style.
    • Favor small, testable functions; keep exported APIs documented with Go-style comments.
    • Maintain ≥80% coverage for non-data packages and ≥90% for data packages when adding new testable code.
  • JavaScript (GitHub Action script):
    • Keep Node 20 compatibility.
    • Uphold strict mode and existing patterns (async helpers, early returns, descriptive errors).
  • Generated site output is not committed; do not add files under out/.

Testing & Validation

  • Preferred commands before submitting Go changes:
    • go test ./...
    • go test -run ^TestStaleRepository$ (mirrors the scheduled workflow focus).
  • For list-only modifications, run linting/formatting on touched files if tools are configured locally.
  • The PR Quality Checks workflow will run .github/scripts/check-quality.js; ensure referenced links in PR bodies are reachable.

Read the full file on GitHub · 54 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 f83e67f6bb7f
  2. 9d ago Changed · +37 tokens per session 24ef17b79b9e
  3. 15d ago Changed · +41 tokens per session a8255c7ff106
  4. 20d ago Changed · +1 lines · +76 tokens per session e5609ba16448
  5. 25d ago Changed · -4 tokens per session a66ae52b2c8b
  6. 2mo ago First seen · 53 lines · 624 tokens per session scan A 0e9e0ffdfc77

Subscribe to this mod's changes

awesome-go AGENTS.md is an instructions file published in the GitHub repository avelino/awesome-go (190,881 stars, last pushed 3d ago), licensed MIT. It adds 774 tokens to every session, about $0.0031 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-30.

Related

Other instructions, from other repositories

awesome-ai-rules copilot-instructions.md

Instructions for Lay4U/awesome-ai-rules, covering github copilot instructions: go, inline completion priorities, go api conventions, interfaces and error patterns.

Lay4U/awesome-ai-rules · 396 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 · 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,461 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