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/using-todnpx skills add theonedev/tod --skill using-todgit 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/using-tod)<a href="https://agentmods.dev/skills/theonedev/tod/using-tod"><img src="https://agentmods.dev/badge/skills/theonedev/tod/using-tod.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.00036 | $0.01090 |
| Opus 5 | $0.00018 | $0.00545 |
| Sonnet 5 | $0.00007 | $0.00218 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
using-tod 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 today.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using the tod CLI
Use the command and consent rules below for general OneDev interactions.
Prerequisites
todis installed and configured withserver-urlandaccess-token.- Project-scoped commands run inside the corresponding OneDev repository.
Command shape
Commands are grouped by resource:
tod issue--list,get,get-comments,create,edit,change-state,link,add-comment,log-work,create-branch,checkout,current-reference,get-query-description,get-valid-fields,get-valid-linkstod pr--list,get,get-comments,get-code-comments,get-builds,get-patch,create,get-title-and-description-requirement,get-commit-message-requirement,edit,approve,request-changes,merge,discard,add-comment,add-code-comment,checkout,get-query-descriptiontod code-comment--add-reply,resolve,unresolve(operates on theidreturned bytod pr get-code-comments)tod build--list,get,get-log,get-code-problems,get-unit-test-report,get-changes-since-success,run(with--branch,--tag, or--local),get-spec-schema,check-spec,get-query-descriptiontod config--set,get,pathtod project--list,current,get,get-query-descriptiontod get-login-name,tod get-unix-timestamp,tod remote,tod get-valid-labels,tod get-commit-message-requirement,tod download,tod version
Commands write the raw OneDev server response to stdout. Run
tod <command> --help for exact flags.
tod build get-code-problems <build-reference> <report-name> <severity-level>
returns found code problems for a build with or higher than the specified
severity. <severity-level> must be one of CRITICAL, HIGH, MEDIUM, or
LOW.
tod build get-unit-test-report <build-reference> <report-name> returns unit
test report data. Pass --artifact <path> to download a report artifact
instead.
CLI reference formats
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.
- today Changed 0d3f0ad52453
- 4d ago First seen · 95 lines · 36 tokens per session scan A de989e8469cc
using-tod is a skill published in the GitHub repository theonedev/tod (14 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,090 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
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…
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.