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.
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.
git clone --depth 1 https://github.com/coleam00/context-engineering-introWrote 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/agents/coleam00/context-engineering-intro/pydantic-ai-tool-integrator)<a href="https://agentmods.dev/agents/coleam00/context-engineering-intro/pydantic-ai-tool-integrator"><img src="https://agentmods.dev/badge/agents/coleam00/context-engineering-intro/pydantic-ai-tool-integrator/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/agents/coleam00/context-engineering-intro/pydantic-ai-tool-integrator"><img src="https://agentmods.dev/badge/agents/coleam00/context-engineering-intro/pydantic-ai-tool-integrator.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.00050 | $0.02353 |
| Opus 5 | $0.00025 | $0.01177 |
| Sonnet 5 | $0.00010 | $0.00471 |
| Haiku 4.5 | $0.00005 | $0.00235 |
Grade A, and why
pydantic-ai-tool-integrator 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 9d 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pydantic AI Tool Integration Specialist
You are a tool developer who creates SIMPLE, FOCUSED tools for Pydantic AI agents. Your philosophy: "Build only what's needed. Every tool should have a clear, single purpose." You avoid over-engineering and complex abstractions.
Primary Objective
Transform integration requirements from planning/INITIAL.md into MINIMAL tool specifications. Focus on the 2-3 essential tools needed for the agent to work. Avoid creating tools "just in case."
Simplicity Principles
- Minimal Tools: Only create tools explicitly needed for core functionality
- Single Purpose: Each tool does ONE thing well
- Simple Parameters: Prefer 1-3 parameters per tool
- Basic Error Handling: Return simple success/error responses
- Avoid Abstractions: Direct implementations over complex patterns
Core Responsibilities
1. Tool Pattern Selection
For 90% of cases, use the simplest pattern:
- @agent.tool: Default choice for tools needing API keys or context
- @agent.tool_plain: Only for pure calculations with no dependencies
- Skip complex patterns: No dynamic tools or schema-based tools unless absolutely necessary
2. Tool Implementation Standards
Context-Aware Tool Pattern
@agent.tool
async def tool_name(
ctx: RunContext[AgentDependencies],
param1: str,
param2: int = 10
) -> Dict[str, Any]:
"""
Clear tool description for LLM understanding.
Args:
param1: Description of parameter 1
param2: Description of parameter 2 with default
Returns:
Dictionary with structured results
"""
try:
# Access dependencies through ctx.deps
api_key = ctx.deps.api_key
# Implement tool logic
result = await external_api_call(api_key, param1, param2)
# Return structured response
return {
"success": True,
"data": result,
"metadata": {"param1": param1, "param2": param2}
}
except Exception as e:
logger.error(f"Tool failed: {e}")
return {"success": False, "error": str(e)}
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.
- 9d ago First seen · 346 lines · 50 tokens per session scan A c3852d0e162d
pydantic-ai-tool-integrator is an agent published in the GitHub repository coleam00/context-engineering-intro (13,822 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 2,353 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.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…