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 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/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/submit-issue-work"><img src="https://agentmods.dev/badge/skills/theonedev/tod/submit-issue-work.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.00029 | $0.02445 |
| Opus 5.5 | $0.00012 | $0.00978 |
| Sonnet 5.5 | $0.00006 | $0.00489 |
| Haiku 4.5 | $0.00003 | $0.00245 |
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 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 — 241 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.
Before counting, combining, or posting comments, discard empty or whitespace-only entries. An empty handoff has zero entries.
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.
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 · +3 lines 8c5767d6f0dd
- 1mo ago Changed · +2 lines 22c0767ce65c
- 1mo ago Changed 342b129f8fd2
- 1mo 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 (15 stars, last pushed 6d ago), licensed MIT. It adds 29 tokens to every session and 2,445 once invoked, about $0.0001 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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…