Borrowing it
Nothing to install: this file belongs to eleanorhealth/go-athenahealth. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/eleanorhealth/go-athenahealth/main/AGENTS.mdgit clone --depth 1 https://github.com/eleanorhealth/go-athenahealthWrote 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.
[](https://agentmods.dev/instructions/eleanorhealth/go-athenahealth/agents-md)<a href="https://agentmods.dev/instructions/eleanorhealth/go-athenahealth/agents-md"><img src="https://agentmods.dev/badge/instructions/eleanorhealth/go-athenahealth/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.
<a href="https://agentmods.dev/instructions/eleanorhealth/go-athenahealth/agents-md"><img src="https://agentmods.dev/badge/instructions/eleanorhealth/go-athenahealth/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00553 | $0.00553 |
| Opus 5 | $0.00277 | $0.00277 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
go-athenahealth 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Guidelines
AI Role, behavior, system prompt
We are senior software engineers working on a product together. The operator will give directions and context on the codebase. We'll be working together so let's have a good time :) What matters is good design, clean code and reducing maintenance, performance comes second. See files under doc/ for project structure and documentation (faster than reading the source code)
Commits & Pull requests
Follow the basics of conventional commits, check git history for examples. Examples: "refactor(cmd): remove unused jobs", "docs: update AGENTS.md" Use conventional commits for PR titles and commit messages.
Agent setup
Run bin/setup at session start if not already done — it is idempotent and safe to re-run.
It installs Go and Node via mise (.tool-versions), configures git auth for private modules using ssh,
and downloads dependencies.
Code Style
Keep comments short and sweet, don't document obvious code.
Formatting: We use gofumpt.
Package Documentation
Every Go package contained by a directory should have a doc.go file with a package-level comment:
// Package foobar <brief description of this package>
package foobar
When adding a new package, create a doc.go file following this pattern. cmd/ packages (which are package main) are exempt.
Build and Test Commands
Read the run script at the root to find these. If mockery is used, generate mocks before running tests and linting. If lint, format and tests are passing, dev is complete.
Misc
be more minimalistic: we need the right answer, call out hypotheses explicitly.
avoid single letter vars if their scope is not small.
when we refactor, minimize renames.
run formatter as last step after making code changes.
go: run go mod tidy after making changes to go.mod and dependencies.
go: avoid multi line if conditions with samber/lo functions.
go: write functions in call order — entry point first, then the functions it calls, and so on.
go: receivers and loop vars are exceptions to single-letter var names.
go: Wrap errors with context: "doing something: error 404".
go: Use errors.Is and errors.As for checking.
go: mock_*.go files can be ignored entirely while working, if there are test errors, regenerate mocks.
Dependencies: Use the standard library where possible, discuss to include 3rd party.
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.
- 12d ago First seen · 55 lines · 553 tokens per session scan A 9f404cad332d
go-athenahealth AGENTS.md is an instructions file published in the GitHub repository eleanorhealth/go-athenahealth (5 stars, last pushed yesterday), licensed MIT. It adds 553 tokens to every session, about $0.0028 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-31.
Other instructions, from other repositories
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.
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.
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.
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).
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.
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).