agents AGENTS.md

A repository instruction file for a collection of reusable coding-agent skills. It explains the folder structure, required files, writing conventions, and available validation process.

In plain words
What is it for?
Use it when maintaining skills in the dcramer/agents repository to understand where files belong, when to add supporting resources, and how to validate changes.
Why use it?
It gives agents consistent rules for creating and updating skills. This helps keep runtime instructions portable, concise, and structurally valid.

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/dcramer/agents/agents-md
Clone the repo
git clone --depth 1 https://github.com/dcramer/agents

Made for: Codex, OpenCode.

Per session 250 This file is loaded in full into every session.
When invoked 250 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.00250 $0.00250
Opus 5 $0.00125 $0.00125
Sonnet 5 $0.00050 $0.00050
Haiku 4.5 $0.00025 $0.00025

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

Security

Grade A, and why

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

What it actually says

Agent Instructions

Repository Shape

  • skills/ contains reusable agent skills.
  • Each skill lives at skills/<name>/.
  • SKILL.md contains runtime instructions and must start with skill frontmatter.
  • spec.md contains the Skillet behavior contract for migrated skills; legacy skills may retain SPEC.md until migrated.
  • SOURCES.md contains provenance, decisions, gaps, and changelog entries.

External References

Need Reference
Repo purpose and installation entrypoint README.md
Skill specification and validation CLI Skillet

Conventions

  • Keep runtime skill guidance portable; use skill-root-relative paths.
  • Add references/, scripts/, or assets/ under a skill only when they have a concrete runtime purpose.
  • Do not add hosting or deployment config, including CNAME, unless explicitly requested.
  • Keep docs concise and actionable; prefer checklists and tables over prose.

Validation

  • No repo package manager or standard test command is defined yet.
  • For skill changes, run the relevant structural validator when available and report the exact command and result.
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 · 25 lines · 250 tokens per session scan A de219ab8c512

Subscribe to this mod's changes

agents AGENTS.md is an instructions file published in the GitHub repository dcramer/agents (54 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 250 tokens to every session, about $0.0013 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.

Related

Other instructions, from other repositories

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.

openai/codex · 5,182 tokens

buildNext

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).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

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).

microsoft/vscode · 5,001 tokens

spec-kit 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.

github/spec-kit · 7,040 tokens

langchain 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.

langchain-ai/langchain · 4,345 tokens