awesome-go AGENTS.md

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

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/avelino/awesome-go/agents-md
Clone the repo
git clone --depth 1 https://github.com/avelino/awesome-go

Made for: Codex, OpenCode.

Per session 624 This file is loaded in full into every session.
When invoked 624 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00624 $0.00624
Opus 5 $0.00312 $0.00312
Sonnet 5 $0.00125 $0.00125
Haiku 4.5 $0.00062 $0.00062

Measured yesterday against content hash 0e9e0ffdfc77, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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

How it starts

The opening of the file, as written. The whole thing — 53 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.23 (see go.mod). 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 · 53 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. yesterday 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 (182,699 stars, last pushed 2d ago), licensed MIT. It adds 624 tokens to every session, about $0.0031 per session on Opus 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.