Borrowing it
Nothing to install: this file belongs to jamestexas/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/jamestexas/agents/main/AGENTS.mdgit clone --depth 1 https://github.com/jamestexas/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/jamestexas/agents/agents-md)<a href="https://agentmods.dev/instructions/jamestexas/agents/agents-md"><img src="https://agentmods.dev/badge/instructions/jamestexas/agents/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/jamestexas/agents/agents-md"><img src="https://agentmods.dev/badge/instructions/jamestexas/agents/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.02391 | $0.02391 |
| Opus 5.5 | $0.00956 | $0.00956 |
| Sonnet 5.5 | $0.00478 | $0.00478 |
| Haiku 4.5 | $0.00239 | $0.00239 |
Grade C, and why
agents AGENTS.md scanned grade C with 1 finding 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 2mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
cp -f source dest mv -f source dest rm -f file rm -rf dir cp -rf src dst How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Codex when working with code in this repository. It is the Codex-facing counterpart to CLAUDE.md; both describe the same repository, and a change to the conventions belongs in both.
Repository Overview
This is an agent definitions repository containing specialized agents. They are consumed by Claude Code and by Codex; the on-disk install target is ~/.claude/ for both, via scripts/install.sh. The repository contains no executable code - only agent definition files in Markdown format with YAML frontmatter.
Agent Development Workflow
Testing Agents Locally
# Copy agent to user directory for testing
cp agent-name.md ~/.claude/agents/
# Or copy to project directory
cp agent-name.md /path/to/project/.claude/agents/
Creating New Agents
-
File Naming: Use kebab-case (e.g.,
code-performance-optimizer.md) -
Required Frontmatter Fields:
name: Must match filename without extensiondescription: Include XML-formatted usage examplesmodel: Usuallyinherit, useopusfor complex reasoningcolor: Choose from blue, green, purple, red, orange
-
Agent Persona Guidelines:
- Create compelling backstory that reinforces expertise
- Define clear methodology and process
- Structure output format for consistency
- Include specific technical focus areas
Quality Standards
- Description: Must include at least 2 detailed usage examples in XML format
- Persona: Should establish credibility and unique perspective
- Process: Define structured approach with numbered steps
- Output: Specify format for agent responses
Repository Structure
/
├── *.md # Agent definition files
├── README.md # Public documentation
├── AGENTS.md # This file
└── .claude/ # agent + skill install target (see scripts/install.sh)
└── settings.local.json # Local permissions
Git Workflow
When committing agent definitions:
- Use semantic commit messages (feat: for new agents, fix: for corrections, docs: for documentation)
- Test agents thoroughly before committing
- Update README.md when adding new agents
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.
- 2mo ago First seen · 236 lines · 2,391 tokens per session scan C 000898db6716
agents AGENTS.md is an instructions file published in the GitHub repository jamestexas/agents (2 stars, last pushed today), licensed Apache-2.0. It adds 2,391 tokens to every session, about $0.0096 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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).
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.
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).
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 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.