What is awesome-claude-code-extensions AGENTS.md?

Repository instructions for maintaining a Python catalogue project. They describe its folders, coding rules, tests, build process, generated files, and link checks.

Use them when editing the catalogue pipeline, running tests, rebuilding outputs, validating results, or checking links.

They give a coding agent the project context needed to make changes consistently and avoid altering generated or reviewed data incorrectly.

How omgits0mar/awesome-claude-code-extensions configures Codex and Ope

Reuse

Borrowing it

Nothing to install: this file belongs to omgits0mar/awesome-claude-code-extensions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/omgits0mar/awesome-claude-code-extensions/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/omgits0mar/awesome-claude-code-extensions

Made for: Codex, OpenCode.

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

README.md

[![agentmods](https://agentmods.dev/badge/instructions/omgits0mar/awesome-claude-code-extensions/agents-md/github.svg)](https://agentmods.dev/instructions/omgits0mar/awesome-claude-code-extensions/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/omgits0mar/awesome-claude-code-extensions/agents-md"><img src="https://agentmods.dev/badge/instructions/omgits0mar/awesome-claude-code-extensions/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/omgits0mar/awesome-claude-code-extensions/agents-md"><img src="https://agentmods.dev/badge/instructions/omgits0mar/awesome-claude-code-extensions/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 574 This file is loaded in full into every session.

When invoked 574 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00574	$0.00574
Opus 5.5	$0.00230	$0.00230
Sonnet 5.5	$0.00115	$0.00115
Haiku 4.5	$0.00057	$0.00057

Measured 2mo ago against content hash e1e4c53b954f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

awesome-claude-code-extensions 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 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.

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

How it starts

The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Project Structure & Module Organization

scripts/ contains the Python catalog pipeline: source parsing, normalization, generation, validation, discovery, and link checking.
tests/ contains standard-library unittest coverage for parsers, URL normalization, merging, CSV safety, and link handling.
research/ holds reviewed source datasets and checksummed upstream snapshots. Treat snapshots as immutable inputs unless intentionally refreshing them.
catalog/ and CATALOG.md are generated outputs, including JSON, CSV, statistics, schema, and per-kind indexes.
docs/ documents methodology, taxonomy, sources, licensing, and safety. GitHub workflows and issue forms live under .github/.

Build, Test, and Development Commands

Use Python 3.10 or newer; runtime code uses only the standard library.

make test               # Run all test_*.py files.
make build              # Regenerate catalog files from committed inputs.
make validate           # Check schema, counts, generated views, and invariants.
make all                # Test, build, then validate.
make check-links        # Check a deterministic 250-link network sample.
make refresh-snapshots  # Fetch upstream inputs; review every resulting diff.

After changing research data or parsers, run make all and commit the regenerated outputs. CI rejects stale generated files.

Coding Style & Naming Conventions

Follow conventional Python style: four-space indentation, snake_case functions and variables, PascalCase test classes, and uppercase module constants. Prefer type hints, pathlib.Path, small pure helpers, deterministic ordering, and standard-library dependencies. Keep catalog descriptions neutral, factual, original, and no longer than the schema permits. Do not hand-edit generated catalog views.

Testing Guidelines

Add focused regression tests in tests/test_<area>.py for parser, normalization, deduplication, safety, or schema changes. Use descriptive test_<behavior> methods. There is no numeric coverage threshold; changed behavior must be exercised directly. Run both make test and make validate before submitting.

Read the full file on GitHub · 41 lines

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.

2mo ago First seen · 41 lines · 574 tokens per session scan A e1e4c53b954f

Subscribe to this mod's changes

awesome-claude-code-extensions AGENTS.md is an instructions file published in the GitHub repository omgits0mar/awesome-claude-code-extensions (4 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 574 tokens to every session, about $0.0023 per session on Opus 5.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.

awesome-claude-code-extensions AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
awesome-claude-code-extensions AGENTS.mdomgits0mar/awesome-claude-code-extensions	Instructions file	4	3mo ago	CC0-1.0	A	574	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

awesome-claude-code-extensions: Instructions file for Codex