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 agents/croakingtoad/context-engineering-mcp/pydantic-ai-plannergit clone --depth 1 https://github.com/croakingtoad/context-engineering-mcpWrote 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/croakingtoad/context-engineering-mcp/pydantic-ai-planner)<a href="https://agentmods.dev/agents/croakingtoad/context-engineering-mcp/pydantic-ai-planner"><img src="https://agentmods.dev/badge/agents/croakingtoad/context-engineering-mcp/pydantic-ai-planner.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.00060 | $0.01493 |
| Opus 5 | $0.00030 | $0.00746 |
| Sonnet 5 | $0.00012 | $0.00299 |
| Haiku 4.5 | $0.00006 | $0.00149 |
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 5d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago First seen · 187 lines · 60 tokens per session scan A 0ac4c9ac6ecc
pydantic-ai-planner is an agent published in the GitHub repository croakingtoad/context-engineering-mcp (11 stars, last pushed 11mo ago), with no licence file. 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.
Other agents, from other repositories
memcp-analyzer
Analyze a MemCP context using the RLM peek-identify-load-analyze pattern. Use proactively when answering questions about stored content without loading it all into the main context.
memcp-entity-extractor
Extract structured entities and relationships from content. Provide the text content to analyze. Use proactively after storing new insights.
memcp-synthesizer
REDUCE phase: synthesize findings from multiple mapper results into a coherent answer. Provide the question and all mapper outputs as input.
memcp-mapper
MAP phase: analyze a single assigned chunk and return structured findings. Provide contextname, chunkindex, and question as input.
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…