jinja2-async-environment: Instructions file for Codex

AGENTS.md

jinja2-async-environment AGENTS.md is an instructions file for Codex, OpenCode from lesleslie/jinja2-async-environment. It costs 557 tokens per session, scanned A, original, BSD-3-Clause.

Repository instructions for the jinja2-async-environment project, covering its layout, coding conventions, build commands, and tests. They explain how to use tools such as uv, pytest, Ruff, and Pyright in that repository.

In plain words
What is it for?
Use them when developing or reviewing this Python project, running targeted or complete tests, checking types and style, or locating source, documentation, and build files.
Why use it?
They give an agent the project's expected workflow and help it avoid editing generated files or running the wrong checks.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is lesleslie/jinja2-async-environment's own configuration. It tells Codex and OpenCode how to work on jinja2-async-environment itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything jinja2-async-environment configures →

Reuse

Borrowing it

Nothing to install: this file belongs to lesleslie/jinja2-async-environment. 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/lesleslie/jinja2-async-environment/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/lesleslie/jinja2-async-environment

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.

agentmods badge for jinja2-async-environment AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/lesleslie/jinja2-async-environment/agents-md/github.svg)](https://agentmods.dev/instructions/lesleslie/jinja2-async-environment/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/lesleslie/jinja2-async-environment/agents-md"><img src="https://agentmods.dev/badge/instructions/lesleslie/jinja2-async-environment/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.

agentmods 80×15 button for jinja2-async-environment AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/lesleslie/jinja2-async-environment/agents-md"><img src="https://agentmods.dev/badge/instructions/lesleslie/jinja2-async-environment/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 557 This file is loaded in full into every session.
When invoked 557 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00557 $0.00557
Opus 5.5 $0.00223 $0.00223
Sonnet 5.5 $0.00111 $0.00111
Haiku 4.5 $0.00056 $0.00056

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

Security

Grade A, and why

jinja2-async-environment 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 1mo 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 · 22 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

jinja2_async_environment/ contains the async environment, loaders, compiler modules, and caching utilities; review environment.py first, then dive into loaders/, compiler_modules/, and caching/ when touching specialization. Tests live in tests/, mirroring package layout with test_*.py files and marker-specific suites. Documentation, changelogs, and benchmarking notes sit in docs/ and topical *.md files at the root. Build artifacts land in dist/; avoid editing generated content directly.

Build, Test & Development Commands

Use UV for dependency management: uv sync bootstraps the virtualenv defined by uv.lock. Run the holistic quality gate with python -m crackerjack -t --ai-agent before sharing changes—it executes lint, type-check, and test bundles. Individual tools remain available: ruff format enforces the 88-character formatter, ruff check handles linting, and pyright runs strict type analysis. Execute pytest (or pytest -m unit / pytest -m integration) for targeted runs; append --cov=jinja2_async_environment when asserting coverage locally.

Coding Style & Naming Conventions

Code targets Python 3.13+ with standard four-space indentation and exhaustive type hints. Follow snake_case for functions, async coroutines, and module names; prefer PascalCase for classes and TypedDicts. Keep async APIs truly non-blocking—wrap sync fallbacks in thread pools when necessary. Let ruff autofix trivial issues, and keep imports sorted per the configured isort profile (no blank line before first-party imports).

Testing Guidelines

Pytest discovers files named test_*.py or *_test.py; align helper modules under the same patterns when practical. Mark tests with @pytest.mark.unit, @pytest.mark.integration, or @pytest.mark.benchmark to integrate with existing selection flags. The default run enforces coverage via --cov-fail-under=83; do not regress this threshold. Prefer async fixtures and the asyncio event loop provided by pytest-asyncio instead of manual loop management.

Read the full file on GitHub · 22 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.

  1. 1mo ago First seen · 22 lines · 557 tokens per session scan A 225851392fbb

Subscribe to this mod's changes

jinja2-async-environment AGENTS.md is an instructions file published in the GitHub repository lesleslie/jinja2-async-environment (6 stars, last pushed 1mo ago), licensed BSD-3-Clause. It adds 557 tokens to every session, about $0.0022 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-09-04.

Related

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens