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/jlevy/simple-modern-uv/agents-mdgit clone --depth 1 https://github.com/jlevy/simple-modern-uvWrote 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/jlevy/simple-modern-uv/agents-md)<a href="https://agentmods.dev/instructions/jlevy/simple-modern-uv/agents-md"><img src="https://agentmods.dev/badge/instructions/jlevy/simple-modern-uv/agents-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 | $0.00765 | $0.00765 |
| Opus 5 | $0.00382 | $0.00382 |
| Sonnet 5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
simple-modern-uv 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 4d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Instructions for AI Agents
This file provides instructions and context for AI coding agents working on this project.
tbd
This repository uses tbd for git-native issue tracking (beads), spec-driven planning, and on-demand engineering guidelines. As the agent, you operate tbd on the user’s behalf — translate their requests into tbd actions rather than telling them to run commands.
- Run
tbd primeto load current project state and the full tbd workflow. - Run
tbd skillfor the complete reusable tbd skill instructions. - Run
tbd shortcut --listandtbd guidelines --listfor on-demand resources. - Track all work as beads:
tbd create,tbd ready,tbd close, andtbd sync.
Build and Test
This is a Copier template repo, not a Python project
itself; there is no pyproject.toml to sync at the root.
Validation means rendering the template and exercising the render:
# Auto-format all Markdown docs (including *.md.jinja); check-only variant for CI:
make format
make format-check
# Render the template non-interactively (smoke test):
SMOKE_DIR=$(mktemp -d)
uvx --exclude-newer "14 days" [email protected] copy --defaults --vcs-ref=HEAD \
--data package_name=smoke-test \
--data package_github_org=testorg . "$SMOKE_DIR"
# Dynamic versioning needs an initial commit before installation:
cd "$SMOKE_DIR"
git init --initial-branch=main
git add .
git -c user.name=Smoke -c [email protected] \
commit -m "Initial commit"
make install
make lint-check
make test
Architecture Overview
template/: the Copier template source that ships to generated projects (*.jinjafiles are rendered; everything else copies as-is). Thetemplate/Makefileandtemplate/devtools/lint.pyare what downstream projects use, not this repo.copier.yml: template questions and validation; the single source of truth for template variables.skills/simple-modern-uv/: the portable agent workflow bundle. ItsSKILL.mdis the concise router; the one-levelreferences/files own the new, selective, migration, and update procedures. Keep README discovery and generated agent guidance aligned with these routes.updating.md: the full maintenance and release flow (downstreamjlevy/simple-modern-uv-templaterepo is the release gate).docs/project/: maintainer research, frozen release evidence, and implementation records.
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.
- 4d ago First seen · 79 lines · 765 tokens per session scan A f223ef898db5
simple-modern-uv AGENTS.md is an instructions file published in the GitHub repository jlevy/simple-modern-uv (299 stars, last pushed 9d ago), licensed MIT. It adds 765 tokens to every session, about $0.0038 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.