Borrowing it
Nothing to install: this file belongs to vstorm-co/pydantic-ai-todo. 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/vstorm-co/pydantic-ai-todo/main/CLAUDE.mdgit clone --depth 1 https://github.com/vstorm-co/pydantic-ai-todoWrote 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/vstorm-co/pydantic-ai-todo/claude-md)<a href="https://agentmods.dev/instructions/vstorm-co/pydantic-ai-todo/claude-md"><img src="https://agentmods.dev/badge/instructions/vstorm-co/pydantic-ai-todo/claude-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.
<a href="https://agentmods.dev/instructions/vstorm-co/pydantic-ai-todo/claude-md"><img src="https://agentmods.dev/badge/instructions/vstorm-co/pydantic-ai-todo/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00417 | $0.00417 |
| Opus 5 | $0.00209 | $0.00209 |
| Sonnet 5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
pydantic-ai-todo 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 11d 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.
What it actually says
CLAUDE.md
Guidance for Claude Code when working on this repository.
What This Project Is
pydantic-ai-todo provides a todo/task planning toolset for pydantic-ai agents. It's designed to work standalone with any agent - no specific deps type required.
Key pattern: Storage Injection - tools use closure to capture state, not ctx.deps.
Commands
uv sync --group dev # Install dependencies
uv run pytest # Run tests
uv run coverage run -m pytest && uv run coverage report # Test with coverage
uv run ruff check . # Lint
uv run ruff format . # Format
uv run pyright # Type check
Structure
pydantic_ai_todo/
├── types.py # Todo, TodoItem models
├── storage.py # TodoStorage, TodoStorageProtocol
├── toolset.py # create_todo_toolset(), get_todo_system_prompt()
└── __init__.py # Public API exports
Core Pattern
def create_todo_toolset(storage=None) -> FunctionToolset[Any]:
_storage = storage or TodoStorage()
@toolset.tool
async def read_todos() -> str: # No ctx - uses closure
return format(_storage.todos)
Requirements
- 100% test coverage - every PR must maintain this
- Type annotations - pyright strict mode
- Async tools - all tool functions are async
Testing
# Run specific test
uv run pytest tests/test_toolset.py::TestCreateTodoToolset -v
# Debug mode
uv run pytest -v -s
Integration
This library is used by pydantic-deep which re-exports its API. Changes here affect pydantic-deep users.
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.
- 11d ago First seen · 62 lines · 417 tokens per session scan A cb342331d5c5
pydantic-ai-todo CLAUDE.md is an instructions file published in the GitHub repository vstorm-co/pydantic-ai-todo (76 stars, last pushed 27d ago), licensed MIT. It adds 417 tokens to every session, about $0.0021 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
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).
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.
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.