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/GEMINI.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/gemini-md)<a href="https://agentmods.dev/instructions/lesleslie/jinja2-async-environment/gemini-md"><img src="https://agentmods.dev/badge/instructions/lesleslie/jinja2-async-environment/gemini-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.00524 | $0.00524 |
| Opus 5 | $0.00262 | $0.00262 |
| Sonnet 5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
jinja2-async-environment GEMINI.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 2d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Overview
This project, jinja2-async-environment, is a Python library that provides an asynchronous version of the popular Jinja2 templating engine. It's designed for use in asynchronous web frameworks like FastAPI, Starlette, and AIOHTTP. The key features include:
- Fully Asynchronous: All template operations (loading, rendering, caching) are non-blocking.
- Jinja2 Compatibility: It aims for 100% compatibility with Jinja2, including macros, inheritance, and filters.
- Performance: The library is optimized for performance, with benchmarks showing it can be faster than the standard Jinja2 in some scenarios.
- Async Loaders: It provides asynchronous versions of Jinja2's template loaders, such as
AsyncFileSystemLoader,AsyncPackageLoader, andAsyncDictLoader. - Bytecode Caching: Supports asynchronous bytecode caching with Redis to improve performance.
- Sandboxed Execution: Includes an
AsyncSandboxedEnvironmentfor safely rendering untrusted templates.
The project is built using modern Python features (Python 3.13+) and is fully type-hinted.
Building and Running
The project uses hatchling for building and pytest for testing.
Installation
To install the package for use in another project:
pip install jinja2-async-environment
For development, you can install it in editable mode with development dependencies:
pip install -e ".[dev]"
Running Tests
Tests are run using pytest. The configuration in pyproject.toml specifies the test paths and options. To run the tests:
pytest
The tests include unit tests, integration tests, and benchmarks. The test coverage is configured to fail if it drops below 69%.
Development Conventions
- Code Style: The project follows the
crackerjackcode style, which is enforced by therufflinter. - Linting:
ruffis used for linting and formatting. The configuration is inpyproject.toml. - Type Checking:
pyrightis used for static type checking in "strict" mode. - Testing:
pytestis the testing framework. Tests are located in thetests/directory. New features should be accompanied by comprehensive tests. - Contributions: The
README.mdfile outlines the contribution process, which includes forking the repository, creating a feature branch, adding tests, and submitting a pull request.
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.
- 2d ago First seen · 49 lines · 524 tokens per session scan A 8362d2e017da
jinja2-async-environment GEMINI.md is an instructions file published in the GitHub repository lesleslie/jinja2-async-environment (6 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 524 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-09-04.
Other instructions, from other repositories
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.
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).
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).
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.
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.