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-issue-worknpx skills add theonedev/tod --skill submit-issue-workgit 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/submit-issue-work)<a href="https://agentmods.dev/skills/theonedev/tod/submit-issue-work"><img src="https://agentmods.dev/badge/skills/theonedev/tod/submit-issue-work.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.02355 |
| Opus 5 | $0.00015 | $0.01177 |
| Sonnet 5 | $0.00006 | $0.00471 |
| Haiku 4.5 | $0.00003 | $0.00235 |
Grade A, and why
submit-issue-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 4d 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submit work on a OneDev issue
Submit code changes and/or saved comments for an issue.
Prerequisites
todis installed and configured.- The current repository belongs to the issue's project.
Session handoff
This workflow pairs with work-on-issue. At the start, recover
<saved-issue-comments> from the same chat session:
- From a prior
work-on-issuerun -- use the exact drafted comment text presented or amended earlier in this session. - From the user's submit prompt -- if the user supplies or revises comment
text when asking to submit, treat that as
<saved-issue-comments>. - Otherwise --
<saved-issue-comments>is empty.
<saved-issue-comments> is session state, not a file on disk and not comments
already on OneDev. Step 7 posts these deferred drafts.
Aborting the workflow
Run the workflow sequentially. Before aborting it for any reason, always follow
this section. If current user is an AI user and <issue-reference> is known,
immediately run
tod issue add-comment <issue-reference> '<reason>' to explain the stop reason.
Report the reason, including the command and error when applicable, and stop.
Interactive questions
If 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 issue comment explaining the blocker or needed decision, then stop:
tod issue add-comment <issue-reference> '<reason>'
Shell quoting for authored text
When passing authored text such as Markdown comments, commit messages, PR
titles, or PR descriptions to 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 the
command receives the text.
Markdown references for issue, pull request, or build
In authored OneDev Markdown, write an entity reference as <type> <reference>,
such as PR #42, issue acme/web#123, or build ACMEWEB-7. With no type, the
reference means an issue. <reference> is #123 for an entity in the current
project, path/to/project#123 for one in another project, or PROJECTKEY-123,
which works from any project as long as the project has a key defined. Keep the
type and reference separated by one space with nothing between them. These
forms differ from tod command arguments.
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.
- 4d ago First seen · 236 lines · 29 tokens per session scan A a894dae5fc1d
submit-issue-work is a skill published in the GitHub repository theonedev/tod (13 stars, last pushed 5d ago), licensed MIT. It adds 29 tokens to every session and 2,355 once invoked, about $0.0001 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
finn-spec
Interview the user about a raw idea until confident, then file a build-ready issue in Linear. Use when asked to run Finn-loop's spec interview, draft a queue-ready issue, or plan a feature. Interactive — requires the user present; never run unattended.