agentmods.dev

go-micro AGENTS.md

A set of repository instructions for coding agents working on the Go Micro project. It describes how to handle requested pull requests, including branches, checks, commits and GitHub submission.

In plain words
What is it for?
Creating a focused branch, running build and test checks, reviewing changes, committing work, opening a GitHub pull request and setting it to merge automatically after required checks pass.
Why use it?
It makes the contribution process consistent and records the checks expected before a change is proposed. It also tells the agent how to prepare a pull request and enable automatic merging.

Instructions file for CodexOpenCode

23k 2d ago A scan 418 tokens original Apache-2.0
View the source file micro/go-micro
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/micro/go-micro/agents-md
Clone the repo
git clone --depth 1 https://github.com/micro/go-micro

Made for: Codex, OpenCode.

Per session 418 This file is loaded in full into every session.
When invoked 418 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.00418 $0.00418
Opus 5 $0.00209 $0.00209
Sonnet 5 $0.00084 $0.00084
Haiku 4.5 $0.00042 $0.00042

Measured yesterday against content hash c325aebd6224, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

go-micro 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 · 40 lines

What it actually says

Repository agent instructions

These instructions apply to the entire repository.

Pull requests from Codex tasks

When a Codex task makes repository changes and the requested outcome is a PR:

  1. Keep the change focused on the assigned issue or prompt.

  2. Run the relevant verification commands and capture their results (go build ./..., go test ./..., golangci-lint run ./...).

  3. Check git status --short and review the diff before finishing.

  4. Create a uniquely-named branch under the codex/ prefix (do not work on master, and do not use a generic name like work):

    git switch -c codex/<issue-number>-<short-slug>

  5. Stage the intended files and commit on that branch.

  6. Open the pull request yourself with the GitHub CLI, which is installed in the environment and whose origin points at this repository, then enable auto-merge so GitHub merges it once the required CI checks pass:

    git push -u origin HEAD
gh pr create --base master --label codex \
  --title "<concise title>" \
  --body "<summary of the change and testing, including 'Closes #<issue>'>"
gh pr merge --squash --auto --delete-branch

The branch should start with codex/ and the PR should carry the codex label. Auto-merge waits for the required status checks (build, tests, golangci-lint) — never merge a PR manually before CI is green.

Do not just say that a PR was opened, and do not rely on the make_pr tool: in this environment make_pr only records the title/body and never pushes a branch or creates a PR. The task is not complete until gh pr create has opened a real pull request and printed its URL.

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 · 40 lines · 418 tokens per session scan A c325aebd6224

Subscribe to this mod's changes

go-micro AGENTS.md is an instructions file published in the GitHub repository micro/go-micro (23,048 stars, last pushed 2d ago), licensed Apache-2.0. It adds 418 tokens to every session, about $0.0021 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.

Code reviewGit and workflowTestingaidistributed-systemsgogolangmicromicroservices
Related

Other instructions, from other repositories

ollama AGENTS.md

Instructions for ollama/ollama, covering agents.md and building.

ollama/ollama · 91 tokens

ollama CLAUDE.md

Instructions for ollama/ollama: See AGENTS.md for the shared agent instructions for this repository.

ollama/ollama · 21 tokens

sq AGENTS.md

Instructions for neilotoole/sq, covering agents.md, about sq, key documents, common commands and conventions.

neilotoole/sq · 3,837 tokens

azure-sdk-for-go go-examples.instructions.md

Instructions for Azure/azure-sdk-for-go, a project described as: This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at.

Azure/azure-sdk-for-go · 113 tokens

azure-sdk-for-go go-code.instructions.md

Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.

Azure/azure-sdk-for-go · 755 tokens

gorest AGENTS.md

Instructions for pilinux/gorest, covering agents.md, project overview, build and run commands, build and tidy dependencies.

pilinux/gorest · 5,194 tokens