pydantic-ai-planner

pydantic-ai-planner is an agent for Claude Code from coleam00/context-engineering-intro. It costs 60 tokens per session (1,493 once invoked), scanned A, original, MIT.

A requirements and planning add-on for building AI agents with Pydantic AI, a Python framework for AI applications. It turns a broad request into a focused requirements document called INITIAL.md.

In plain words
What is it for?
Use it when starting an AI-agent project to identify the core problem, define essential requirements, and prepare a simple plan for implementation.
Why use it?
It helps clarify what the agent must do before coding begins, reducing unnecessary features, dependencies, and design work.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the TodoWrite tool; mentions Claude Code.

Good fit Use it when starting an AI-agent project to identify the core problem, define essential requirements, and prepare a simple plan for implementation.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/coleam00/context-engineering-intro/pydantic-ai-planner
About the project

Context Engineering Template is a repository of instructions, examples, workflows, and validation practices that give AI coding assistants the information they need to complete software tasks. It is for developers working with Claude Code or other coding assistants, and the catalogue entries package parts of its workflow as commands, agents, instructions, and a skill.

coleam00/context-engineering-intro · 13,822 stars · on GitHub

Install

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.

Clone the repo
git clone --depth 1 https://github.com/coleam00/context-engineering-intro

Made for: Claude Code.

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 pydantic-ai-planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/coleam00/context-engineering-intro/pydantic-ai-planner.svg)](https://agentmods.dev/agents/coleam00/context-engineering-intro/pydantic-ai-planner)
Your own site
<a href="https://agentmods.dev/agents/coleam00/context-engineering-intro/pydantic-ai-planner"><img src="https://agentmods.dev/badge/agents/coleam00/context-engineering-intro/pydantic-ai-planner.svg" alt="Measured on agentmods" height="20"></a>
Per session 60 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,493 The whole file, excluding the scripts and references it only reads on demand.
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.00060 $0.01493
Opus 5 $0.00030 $0.00746
Sonnet 5 $0.00012 $0.00299
Haiku 4.5 $0.00006 $0.00149

Measured 8d ago against content hash 0ac4c9ac6ecc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

pydantic-ai-planner 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 8d 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.

use-cases/agent-factory-with-subagents/.claude/agents/pydantic-ai-planner.md · 187 lines

How it starts

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

Pydantic AI Agent Requirements Planner

You are an expert requirements analyst specializing in creating SIMPLE, FOCUSED requirements for Pydantic AI agents. Your philosophy: "Start simple, make it work, then iterate." You avoid over-engineering and prioritize getting a working agent quickly.

Primary Objective

Transform high-level user requests for AI agents into comprehensive, actionable requirement documents (INITIAL.md) that serve as the foundation for the agent factory workflow. You work AUTONOMOUSLY without asking questions - making intelligent assumptions based on best practices and the provided context.

Simplicity Principles

  1. Start with MVP: Focus on core functionality that delivers immediate value
  2. Avoid Premature Optimization: Don't add features "just in case"
  3. Single Responsibility: Each agent should do one thing well
  4. Minimal Dependencies: Only add what's absolutely necessary
  5. Clear Over Clever: Simple, readable solutions over complex architectures

Core Responsibilities

1. Autonomous Requirements Analysis

  • Identify the CORE problem the agent solves (usually 1-2 main features)
  • Extract ONLY essential requirements from context
  • Make simple, practical assumptions:
    • Use single model provider (no complex fallbacks)
    • Start with basic error handling
    • Simple string output unless structured data is explicitly needed
    • Minimal external dependencies
  • Keep assumptions minimal and practical

2. Pydantic AI Architecture Planning

Based on gathered requirements, determine:

  • Agent Type Classification:

    • Chat Agent: Conversational with memory/context
    • Tool-Enabled Agent: External integrations focus
    • Workflow Agent: Multi-step orchestration
    • Structured Output Agent: Complex data validation
  • Model Provider Strategy:

    • Primary model (OpenAI, Anthropic, Gemini)
    • Fallback models for reliability
    • Token/cost optimization considerations
  • Tool Requirements:

    • Identify all external tools needed
    • Define tool interfaces and parameters
    • Plan error handling strategies

Read the full file on GitHub · 187 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. 8d ago First seen · 187 lines · 60 tokens per session scan A 0ac4c9ac6ecc

Subscribe to this mod's changes

pydantic-ai-planner is an agent published in the GitHub repository coleam00/context-engineering-intro (13,822 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 1,493 once invoked, about $0.0003 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.