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 skills add mitodl/agent-kit --skill create-ol-pull-requestgit clone --depth 1 https://github.com/mitodl/agent-kitWrote 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/mitodl/agent-kit/create-ol-pull-request)<a href="https://agentmods.dev/skills/mitodl/agent-kit/create-ol-pull-request"><img src="https://agentmods.dev/badge/skills/mitodl/agent-kit/create-ol-pull-request/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/mitodl/agent-kit/create-ol-pull-request"><img src="https://agentmods.dev/badge/skills/mitodl/agent-kit/create-ol-pull-request.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.00132 | $0.04251 |
| Opus 5.5 | $0.00053 | $0.01700 |
| Sonnet 5.5 | $0.00026 | $0.00850 |
| Haiku 4.5 | $0.00013 | $0.00425 |
Grade C, and why
create-ol-pull-request scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- testing instructions --> How it starts
The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a Pull Request (/olpr)
Guides creating a PR in a repo with a github.com/mitodl/ remote (check
git remote -v) using the org's standard pull request template.
Step 1 — Inspect the branch and diff
Before prompting the user, gather context automatically. The base is the
repo's default branch unless the user names a different target; use the
same <base> everywhere below, since origin/HEAD is wrong for a PR
against a release branch.
git --no-pager branch --show-current
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'
git fetch origin <base>
git --no-pager log --oneline origin/<base>..HEAD
git --no-pager diff --shortstat origin/<base>...HEAD
# Existing PR for this branch (also returns closed/merged ones; check state)
gh pr view --json url,title,state 2>/dev/null
- If an open PR already exists for the branch, share its URL and stop. Don't create a duplicate.
- If there are no commits ahead of the base, warn the user before proceeding.
Step 2 — Gather PR metadata
Ask the user for each field in a single batched question, rather than inferring the body and asking them to correct it:
| Field | How to obtain |
|---|---|
| Title | Ask the user; offer one derived from the branch name / commits as a default they can overwrite |
| Linked tickets | Ask for issue numbers (Closes #, Fixes #, or N/A) |
| Description | Ask what the PR does; summarise from commits only if the user says "summarise"; summary should be short and high level; put detailed technical explanation of the PR in the <details> block |
| Screenshots | Ask only when the diff touches UI code; images get attached after the PR is created |
| Testing notes | Ask how the changes were tested and how a reviewer can validate |
| Additional context | Ask for reviewer notes, caveats, or checklist items |
| Draft? | Ask if this should be a draft PR (default: no; suggest yes if the user calls it a work in progress) |
What ships with it
1 file 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.
- 8d ago Changed · +21 lines ca262a29c29b
- 17d ago Changed · -33 lines · +27 tokens per session b9c710ebb582
- 25d ago Changed · +126 lines · +30 tokens per session 5f6170da7a8c
- 1mo ago First seen · 258 lines · 75 tokens per session scan C 6251ceba8609
create-ol-pull-request is a skill published in the GitHub repository mitodl/agent-kit (5 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 132 tokens to every session and 4,251 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.