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 skills/theonedev/tod/submit-pull-request-worknpx skills add theonedev/tod --skill submit-pull-request-workgit clone --depth 1 https://github.com/theonedev/todWhat 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.00032 | $0.02133 |
| Opus 5 | $0.00016 | $0.01066 |
| Sonnet 5 | $0.00006 | $0.00427 |
| Haiku 4.5 | $0.00003 | $0.00213 |
Grade A, and why
submit-pull-request-work 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 2d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submit pull request work
Submit code changes and/or saved comments for an existing pull request. This workflow does not create a pull request.
Prerequisites
todis installed and configured.- The current repository belongs to the PR's source or target project.
Session handoff
This workflow pairs with work-on-pull-request. At the start, recover
<saved-pr-actions> from the same chat session:
- From a prior
work-on-pull-requestrun -- use the exact drafted actions presented or amended earlier in this session, including comment text and parameters (comment-id, file, line range, approve/request-changes, merge, etc.). - From the user's submit prompt -- if the user supplies or revises actions
when asking to submit, treat that as
<saved-pr-actions>. - Otherwise --
<saved-pr-actions>is empty.
<saved-pr-actions> is session state, not a file on disk and not discussion
already on OneDev. Step 5 applies these deferred drafts.
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 and <pr-reference> is known,
immediately run
tod pr add-comment <pr-reference> '<reason>' to explain the stop reason.
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, post a concise PR comment explaining the blocker or needed decision, then stop:
tod pr add-comment <pr-reference> '<reason>'
Shell quoting for authored text
When passing authored text such as Markdown comments, review notes, summaries,
or commit messages to tod from a shell command, quote it so the shell
preserves it literally. Prefer a single-quoted argument, and escape any literal
single quote inside the text as '\''. Do not wrap text containing backticks in
double quotes, as the shell will treat backticks as command substitution before
tod receives the text.
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.
- 2d ago First seen · 208 lines · 32 tokens per session scan A 0bc5beeee0fb
submit-pull-request-work is a skill published in the GitHub repository theonedev/tod (13 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 2,133 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.