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 edit-build-specgit 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/edit-build-spec)<a href="https://agentmods.dev/skills/theonedev/tod/edit-build-spec"><img src="https://agentmods.dev/badge/skills/theonedev/tod/edit-build-spec.svg" alt="Measured on agentmods" 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.00038 | $0.00631 |
| Opus 5 | $0.00019 | $0.00316 |
| Sonnet 5 | $0.00008 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
edit-build-spec 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 8d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edit OneDev CI/CD spec
Author or update .onedev-buildspec.yml for the current OneDev project.
Prerequisites
todis installed and configured.- The current directory is the project root where
.onedev-buildspec.ymlbelongs.
Workflow
- Fetch the spec schema first. Before editing anything, get the authoritative
spec schema so the generated YAML matches the server's expectations:
tod build get-spec-schema - If a CI/CD spec already exists, validate and upgrade it first:
This both validates and upgrades the file to the latest version when needed.tod build check-spec - Inspect the project. Read the files you need (package manifests, language version files, Dockerfiles, etc.) to understand what image and commands the job should use.
- Edit
.onedev-buildspec.ymlapplying the user's instruction and the rules below. - Validate again after editing:
Keep iterating untiltod build check-spectod build check-specsucceeds.
Authoring rules
When writing or modifying .onedev-buildspec.yml:
- A checkout step is generally needed to clone repository into job working directory
- Always call
tod build get-spec-schemafirst so the YAML you produce matches the spec schema. - If a
commandstep is used, enable "run in container" unless the user explicitly asks otherwise. - Different steps run in isolated environments and only share the job working directory. Installing dependencies in one step and running commands that rely on them in another will not work. Keep them in a single step unless the user explicitly wants them separated.
- If a
cachestep is used:- Place it before the step that builds or tests the project.
- If the project has lock files (
package.json,pom.xml, etc.):- Configure checksum files using these lock files.
- Configure the upload strategy as
UPLOAD_IF_NOT_HIT.
- To pass files between jobs, have the producing job publish them with the publish-artifact step, and let consuming jobs pull them in via a job dependency.
- Call
tod build check-specbefore editing an existing CI/CD spec to make sure it is valid and up to date. - Inspect the relevant project files to decide which docker image and commands to use when the user asks you to set up build or test steps.
- Call
tod build check-specagain after editing so the final spec is confirmed valid.
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.
- 8d ago First seen · 67 lines · 38 tokens per session scan A c35e2055938d
edit-build-spec is a skill published in the GitHub repository theonedev/tod (14 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 631 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
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.