Borrowing it
Nothing to install: this file belongs to bordenet/golden-agents. 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/bordenet/golden-agents/main/AGENTS.mdgit clone --depth 1 https://github.com/bordenet/golden-agentsWrote 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/bordenet/golden-agents/agents-md)<a href="https://agentmods.dev/instructions/bordenet/golden-agents/agents-md"><img src="https://agentmods.dev/badge/instructions/bordenet/golden-agents/agents-md.svg" alt="Measured on agentmods" 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.01987 | $0.01987 |
| Opus 5 | $0.00993 | $0.00993 |
| Sonnet 5 | $0.00397 | $0.00397 |
| Haiku 4.5 | $0.00199 | $0.00199 |
Grade A, and why
golden-agents 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 8d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guidelines - Golden Agents Framework
Last Updated: 2026-02-02 Purpose: Teach AI assistants how to USE this framework to apply AI guidance to other repos
🚨 CRITICAL: How to Use This Framework
You are an AI assistant reading this file. This repo contains tools that generate AGENTS.md files for OTHER projects. When a user asks you to "apply golden-agents" or "set up AI guidance" for a repo, follow these instructions.
Step 1: Determine the Target Repo's State
Run the generator with --path pointing to the target repo:
# From this repo's directory (e.g., ~/.golden-agents or wherever cloned)
./generate-agents.sh --path=/path/to/target/repo --dry-run
The script will auto-detect the situation and tell you what to do.
Step 2: Follow the Script's Guidance
| Situation | Script Output | Your Action |
|---|---|---|
| No AGENTS.md | Prompts for --language |
Run with language flag, review output |
| Existing CLAUDE.md/CODEX.md | Suggests --migrate |
Run migrate, then execute the generated prompt |
| Existing AGENTS.md (no markers) | Suggests --adopt |
Run adopt, then execute the generated prompt |
| Existing AGENTS.md (with markers) | Suggests --upgrade |
Run upgrade preview, then --apply if good |
| Bloated AGENTS.md (>250 lines) | Suggests --dedupe |
Run dedupe, then execute the generated prompt |
Step 3: Execute Generated Prompts
THIS IS CRITICAL. The scripts generate prompt files (e.g., MIGRATION-PROMPT.md, ADOPT-PROMPT.md) that YOU must read and execute.
# After running --migrate or --adopt or --dedupe:
cat /path/to/target/repo/MIGRATION-PROMPT.md # or ADOPT-PROMPT.md
Read the prompt file and follow its instructions. These prompts guide you through:
- Deduplicating content
- Preserving project-specific guidance
- Removing redundant framework content
- Organizing into the right structure
Step 4: Verify Zero Data Loss
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.
- 8d ago First seen · 240 lines · 1,987 tokens per session scan A af9623bc0b51
golden-agents AGENTS.md is an instructions file published in the GitHub repository bordenet/golden-agents (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,987 tokens to every session, about $0.0099 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
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).
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).
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.
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.