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/work-on-issuenpx skills add theonedev/tod --skill work-on-issuegit 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-issue)<a href="https://agentmods.dev/skills/theonedev/tod/work-on-issue"><img src="https://agentmods.dev/badge/skills/theonedev/tod/work-on-issue.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.1 | $0.00029 | $0.01833 |
| Opus 5 | $0.00015 | $0.00916 |
| Sonnet 5 | $0.00006 | $0.00367 |
| Haiku 4.5 | $0.00003 | $0.00183 |
Grade A, and why
work-on-issue 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work on a OneDev issue
Read relevant context, prepare work environment, and implement the work.
Prerequisites
todis installed and configured.- The current repository belongs to the issue's project.
Session handoff
This workflow pairs with submit-issue-work. Hand off work within the same
chat session using two channels:
| Work product | Handoff |
|---|---|
| Code changes | Uncommitted changes in the issue checkout, including changed submodules |
| Issue comments | Drafted comment text held in session as <saved-issue-comments> |
When you draft issue comments, treat each one as saved for later
submission -- not merely presentation text. Keep the exact wording you intend
to post. A later submit-issue-work run in this session must be able to
retrieve <saved-issue-comments> and post them in its step 7.
Do not write comment drafts to OneDev in this workflow.
Aborting the workflow
Run the workflow sequentially. Before aborting it for any reason, always follow
this section. If current user is an AI user, draft an issue comment explaining
the stop reason and save it in <saved-issue-comments>. 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, draft a concise issue comment explaining the blocker or needed
decision, save it in <saved-issue-comments>, and stop. Otherwise, ask the
current user when an interactive decision is required.
Workflow
Given an optional <issue-reference> (e.g. 123, #123, myproject#123,
or PROJ-123):
- Resolve the issue reference. If the user prompt or session context
already provides
<issue-reference>, use it. Otherwise derive it from the working directory:
Save non-empty output astod issue current-reference<issue-reference>. If the output is empty, stop and report that the issue reference could not be derived.
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 Changed 25aef3084998
- 6d ago First seen · 181 lines · 29 tokens per session scan A 5f62debaddd3
work-on-issue is a skill published in the GitHub repository theonedev/tod (14 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 1,833 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.