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.
curl -O https://raw.githubusercontent.com/lesleslie/jinja2-async-environment/main/CLAUDE.mdgit clone --depth 1 https://github.com/lesleslie/jinja2-async-environmentWrote 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/lesleslie/jinja2-async-environment/claude-md)<a href="https://agentmods.dev/instructions/lesleslie/jinja2-async-environment/claude-md"><img src="https://agentmods.dev/badge/instructions/lesleslie/jinja2-async-environment/claude-md.svg" alt="Measured on agentmods" 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.00587 | $0.00587 |
| Opus 5 | $0.00293 | $0.00293 |
| Sonnet 5 | $0.00117 | $0.00117 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
jinja2-async-environment CLAUDE.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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
For a shorter, tool-neutral bootstrap document, start with AGENTS.md.
Project Overview
jinja2-async-environment is an async-first extension of Jinja2 aimed at preserving Jinja compatibility while making template loading, compilation, and rendering work well in async applications.
Important goals:
- preserve expected Jinja behavior unless a change is explicitly async-specific
- keep async paths genuinely non-blocking
- protect the package's performance-sensitive code paths
Key Paths
jinja2_async_environment/environment.py: main async environmentjinja2_async_environment/loaders/: async loader implementationsjinja2_async_environment/compiler_modules/: code generation and compiler helpersjinja2_async_environment/caching/: cache management and strategiestests/: unit, integration, benchmark, and regression coverage
Development Commands
Setup
uv sync
Standard Quality Gate
python -m crackerjack -t --ai-agent
Run that before considering work complete. For targeted iteration, use:
ruff format
ruff check
pyright
pytest
pytest -m unit
pytest -m integration
pytest --cov=jinja2_async_environment
Architecture Notes
The package is organized around four concerns:
- environment orchestration
- async loaders
- compiler/codegen helpers
- caching and bytecode support
When making changes:
- prefer extending the modular subsystems instead of rebuilding monolithic logic
- preserve compatibility expectations for sync behavior, macro behavior, and loader contracts
- keep async work non-blocking and isolate any unavoidable sync fallback clearly
- treat performance-sensitive helpers as hot paths and benchmark them when behavior changes
Performance Guidance
This repo cares about performance as a product feature. Be careful around:
- loader caching behavior
- compiler dependency resolution
- template compilation caches
- async iteration and render hot paths
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 · 93 lines · 587 tokens per session scan A a4728fda4d15
jinja2-async-environment CLAUDE.md is an instructions file published in the GitHub repository lesleslie/jinja2-async-environment (6 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 587 tokens to every session, about $0.0029 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-09-04.
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.
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.
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).
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.