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 theonedev/tod --skill work-on-pull-requestgit clone --depth 1 https://github.com/theonedev/todWrote 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/theonedev/tod/work-on-pull-request)<a href="https://agentmods.dev/skills/theonedev/tod/work-on-pull-request"><img src="https://agentmods.dev/badge/skills/theonedev/tod/work-on-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/theonedev/tod/work-on-pull-request"><img src="https://agentmods.dev/badge/skills/theonedev/tod/work-on-pull-request.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.00050 | $0.03129 |
| Opus 5.5 | $0.00020 | $0.01252 |
| Sonnet 5.5 | $0.00010 | $0.00626 |
| Haiku 4.5 | $0.00005 | $0.00313 |
Grade A, and why
work-on-pull-request 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 1mo 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work on a OneDev pull request
Prepare the correct checkout from the user's request, read the relevant context, and perform the work.
Prerequisites
todis installed and configured.- The current repository belongs to the PR's source or target project.
Session handoff
This workflow pairs with submit-pull-request-work. Hand off work within the
same chat session using two channels:
| Work product | Handoff |
|---|---|
| Code changes, including merge-conflict resolutions | Uncommitted changes in the PR source repository and changed submodules |
| PR discussion, review, and merge actions | Ordered list held in session as <saved-pr-actions> |
<saved-pr-actions> is initially empty. Never save a text-posting action with
empty, whitespace-only, or placeholder content. Omit blank optional notes or
summaries without discarding the state-change action.
When you draft PR comments, code-comment replies, resolve/unresolve actions,
approve/request-changes outcomes, or merge actions, treat each one as saved
for later submission -- not merely presentation text. Keep the exact wording
and parameters (file, line range, comment-id, etc.) you intend to apply. A
later submit-pull-request-work run in this session must be able to retrieve
<saved-pr-actions> and apply them in its step 5.
Do not run any tod command that changes PR discussion, review state, or merge
state in this workflow. Do not commit or push code changes; submission handles
both.
Aborting the workflow
Run the workflow sequentially. Before aborting it for any reason, always follow
this section. If the current user is an AI user, draft a PR comment explaining
the stop reason and save it as general PR feedback in <saved-pr-actions>.
Report the reason, including the command and error when applicable, and stop.
Interactive questions
If the current user is an AI user, do not ask the
current user for direction in this workflow. When you would otherwise ask a
question, draft a concise PR comment explaining the blocker or needed decision,
save it as a general PR feedback action in <saved-pr-actions>, and stop.
Otherwise, ask the current user when an interactive decision is required.
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.
- 1mo ago Changed 09df66549ee1
- 1mo ago Changed · +4 lines 1b1cf978b4ea
- 1mo ago Changed · +1 lines 3451fbec76d6
- 1mo ago Changed · +2 lines 6b44f85c3685
- 2mo ago First seen · 271 lines · 50 tokens per session scan A f34c227cdb7f
work-on-pull-request is a skill published in the GitHub repository theonedev/tod (15 stars, last pushed 8d ago), licensed MIT. It adds 50 tokens to every session and 3,129 once invoked, about $0.0002 per session on Opus 5.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
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
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.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…