Borrowing it
Nothing to install: this file belongs to pydantic/pydantic-ai-harness. 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-harness/main/.agents/skills/branch-context/SKILL.mdgit clone --depth 1 https://github.com/pydantic/pydantic-ai-harnessWrote 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-harness/branch-context)<a href="https://agentmods.dev/skills/pydantic/pydantic-ai-harness/branch-context"><img src="https://agentmods.dev/badge/skills/pydantic/pydantic-ai-harness/branch-context/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-harness/branch-context"><img src="https://agentmods.dev/badge/skills/pydantic/pydantic-ai-harness/branch-context.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.01633 |
| Opus 5 | $0.00026 | $0.00816 |
| Sonnet 5 | $0.00011 | $0.00327 |
| Haiku 4.5 | $0.00005 | $0.00163 |
Grade A, and why
branch-context 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.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Branch Context
This directory is the home for durable PR/branch state that outlives a single session. Three surfaces:
| File / dir | Role | Lifetime |
|---|---|---|
issue-brief.md |
Synthesis of the issue(s) this branch addresses | Rewritten only when adopting or re-syncing a branch |
pr-decisions.md |
Append-only log of non-obvious PR-shaping decisions | Append forever; supersede, never edit |
handoffs/ + handoffs-index.md |
Append-only session handoffs for the next agent | Never overwrite a handoff file; index points at the latest |
The instances (issue-brief.md, pr-decisions.md, handoffs-index.md,
handoffs/) are per-branch and git-ignored. The scaffolding (this file, the
scripts, the *.template.md files) is committed. Instantiate the instances from
the templates, or via /adopt-pr when a PR already exists.
Session defaults
On start, before coding:
- Confirm the branch matches the brief's
branch:field (git rev-parse --abbrev-ref HEAD). - Read
issue-brief.md,pr-decisions.md, andhandoffs-index.md. - Read the latest handoff -- the last entry in
handoffs-index.mdpoints at its file underhandoffs/. That is what the previous session left for you. If the index has no entries, there is no handoff yet; start from the brief. - If the brief is still the unfilled template, populate it first: run
/adopt-prwhen a PR already exists, or write it from the linked issue when starting fresh.
While working -- persist without being asked:
- A non-obvious decision (picking path A over B, a plan deviation, an ambiguous
thread resolution) goes into
pr-decisions.mdviaappend-pr-decision.shin the same turn you make it, not "later". - Disk in this directory is the continuity channel, not chat history. Do not rely on the conversation surviving a context clear or a new session.
- Do not write a handoff because the context "feels full" -- that misjudges and primes an early stop. Write a handoff only when the user asks, or when session turnover is already decided (the user is clearing, switching tools, or ending the sitting).
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 168 lines · 53 tokens per session scan A 3c6fc6fdb68a
branch-context is a skill published in the GitHub repository pydantic/pydantic-ai-harness (877 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,633 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
git-ai-search
Search and restore AI conversation context from git history.
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.
release
Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.
mulch-record-from-evidence
Turn the evidence of a finished work session — git commits, changed files, recently-touched seeds issues — into well-formed ml record invocations. Use at session close, when an agent has made changes worth preserving as mulch expertise but hasn't yet recorded them.
release-finalizer
Merges a release PR, associates it with resolved issues, replies to issue reporters, and closes issues. Use after PR review is complete and ready for merge. Closes the release cycle.
release-prep
Orchestrates the full release preparation flow for a plugin — version sync across 7+ files, bilingual release notes creation, and commit message drafting. Use before submitting a PR. Does NOT push or create a PR; that is handled by pr-submitter.