Pydantic AI is a typed Python SDK for building AI agents that can use different language models and interfaces, including voice, image generation, and embeddings. Developers use it for applications ranging from structured data extraction to long-running multi-agent work. The catalogue entries provide workflows and configuration for its coding-agent and harness features.
Borrowing it
Nothing to install: this file belongs to pydantic/pydantic-ai. 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/pydantic/pydantic-ai/main/.agents/skills/pushing-commits-to-the-repo/SKILL.mdgit clone --depth 1 https://github.com/pydantic/pydantic-aiWrote 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/skills/pydantic/pydantic-ai/pushing-commits-to-the-repo)<a href="https://agentmods.dev/skills/pydantic/pydantic-ai/pushing-commits-to-the-repo"><img src="https://agentmods.dev/badge/skills/pydantic/pydantic-ai/pushing-commits-to-the-repo/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/skills/pydantic/pydantic-ai/pushing-commits-to-the-repo"><img src="https://agentmods.dev/badge/skills/pydantic/pydantic-ai/pushing-commits-to-the-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.01771 |
| Opus 5 | $0.00026 | $0.00886 |
| Sonnet 5 | $0.00011 | $0.00354 |
| Haiku 4.5 | $0.00005 | $0.00177 |
Grade A, and why
pushing-commits-to-the-repo 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pushing-commits-to-the-repo
Pushing starts a loop; it does not end the task. Work stops only when CI is green AND no comment is left unresolved.
When you open the PR
Write the title and body
Follow the title and template rules in the root AGENTS.md.
Keep visible body content within 40 lines. Exclude template lines and collapsed <details>
contents from the count. For a feature or behavior change, use this order:
- Why we make these changes — State the problem and decision in a few sentences. Link the issue.
- New public surface — List each new maintained symbol. Write
nonewhen there is none. - User-visible behavior — Show the smallest before-and-after example. Replace it with a call-path diff when the changed call chain explains the behavior; do not include both.
- Verification — Link the exact proving tests from the PR diff. Put a minimal runnable
playground in
<details>only when it helps reviewers reproduce the behavior. - What changes for existing users — State the effect in one sentence.
Nothingis valid.
Use one collapsed <details> section per goal only when the PR has multiple independent goals.
For a trivial PR, use the issue link, a short summary, and the test plan.
User-visible call-path diff
Use one fenced diff tree from the public entry point to the changed observable result.
- Format each node as
path/file.py :: Class.method()orpath/file.py :: function(). - Indent each callee beneath its caller with
└─. Preserve enough unchanged nodes to show each edge. - Collapse irrelevant intermediate calls as
… unchanged machinery …. - Include arguments only when they explain the change.
- Include results only on relevant leaves.
- Keep the shared caller prefix unmarked. Mark only diverging nodes, relevant arguments, or results.
- Target 12 content lines inside the fence. Never exceed 20; collapse secondary branches instead.
Apply a label — the repo triages and filters by them. Fetch the real list first with
gh label list --limit 100, because the set changes and a guessed label silently fails to
apply. Pick the one naming what the PR is (bug, feature, docs, chore, refactor) and
add a topic label (anthropic, MCP, evals, …) where one fits:
gh pr edit <number> --add-label <label>.
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 Changed · +5 lines b2998a76f53c
- 13d ago First seen · 121 lines · 53 tokens per session scan A 65536cd0d165
pushing-commits-to-the-repo is a skill published in the GitHub repository pydantic/pydantic-ai (19,869 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,771 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 skills, from other repositories
parallel-pr-review
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
review-readiness
PR readiness dashboard — tracks which reviews have been completed per branch and gates merge decisions. Shows code review, tests, security, QA, and linting status.
agent-swarm-pr
Agent skill for swarm-pr - invoke with $agent-swarm-pr.
agent-pr-manager
Agent skill for pr-manager - invoke with $agent-pr-manager.
agent-github-pr-manager
Agent skill for github-pr-manager - invoke with $agent-github-pr-manager.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.