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.
npx agentmods add instructions/rlajous/claude-code-commands/agents-mdgit clone --depth 1 https://github.com/rlajous/claude-code-commandsWhat 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 | $0.00516 | $0.00516 |
| Opus 5 | $0.00258 | $0.00258 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
claude-code-commands 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 3d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow contributor guidance
This repository ships the same workflow skills to Claude Code and Codex. Keep shared instructions host-neutral and preserve compatibility for both runtimes.
Source of truth
skills/*/SKILL.mdcontains the 21 shared workflow skills and their canonical bundled resources.agents/*.mdcontains the eight canonical agent instructions..codex/agents/*.tomlis generated bynode scripts/generate-codex-agents.mjs; never edit those files by hand..git-workflow/config.yamland.git-workflow/state files are canonical. Read matching legacy.claude/files only as backward-compatible fallbacks.hooks/review-commit.shis shared. Thenotificationsskill owns the generic notifier, unified GitHub daemon, configuration parser, and Stop-hook adapter. Host-specific registration lives inhooks/claude-hooks.jsonandhooks/hooks.json.
Runtime conventions
- Document Claude invocation as
/skill-nameand Codex invocation as$skill-name. - Describe actions such as asking the user, searching the web, or delegating without naming host-specific tools.
- Resolve bundled resources from the absolute path of the loaded
SKILL.md. Derive the package root from that skill directory only for package-wide assets. AcceptPLUGIN_ROOT, thenCLAUDE_PLUGIN_ROOT, only as verified compatibility fallbacks when a host cannot expose the loaded path. - Keep deterministic helpers in the owning skill's
scripts/orassets/directory. Rootscripts/*entries may be compatibility wrappers, but skills must never silently fall back to/scriptsor use a root wrapper as their canonical implementation. - Preserve Claude-specific frontmatter where Claude requires it. Codex uses
nameanddescriptionfrom each skill plus the generated TOML agent definitions. - Routine edits stay in the main session. Only review, release validation/version comparison, and sufficiently large QA execution workflows delegate to named 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.
- 3d ago First seen · 44 lines · 516 tokens per session scan A 124c7c724529
claude-code-commands AGENTS.md is an instructions file published in the GitHub repository rlajous/claude-code-commands (30 stars, last pushed 4d ago), licensed MIT. It adds 516 tokens to every session, about $0.0026 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.
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).
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.
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.
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).
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.