A command-line interface for d1v.ai projects and container workspaces. It handles authentication, project connections, workspace file synchronisation, container commands, previews, deployment status, and confirmed production releases.

Use it to check login and project state, preview synchronisation changes, pull or push workspace files, run container commands, inspect deployments, and release approved changes.

It keeps project and deployment operations in a repeatable command-line workflow while requiring checks before changing files or releasing to production.

d1v — Skill for Claude Code and Codex by d1vai/d1v-cli

Install

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.

Any agent

npx skills add d1vai/d1v-cli --skill d1v

Clone the repo

git clone --depth 1 https://github.com/d1vai/d1v-cli

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/d1vai/d1v-cli/d1v/github.svg)](https://agentmods.dev/skills/d1vai/d1v-cli/d1v)

Your own site

<a href="https://agentmods.dev/skills/d1vai/d1v-cli/d1v"><img src="https://agentmods.dev/badge/skills/d1vai/d1v-cli/d1v/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/d1vai/d1v-cli/d1v"><img src="https://agentmods.dev/badge/skills/d1vai/d1v-cli/d1v.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,238 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00057	$0.01238
Opus 5.5	$0.00023	$0.00495
Sonnet 5.5	$0.00011	$0.00248
Haiku 4.5	$0.00006	$0.00124

Measured 1mo ago against content hash 3a8e45ec42f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

d1v 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.

skills/d1v/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

d1v CLI

Use the installed d1v command. For automation and structured inspection, use --format json; never mix JSON output with an interactive shell.

Safety

Never print, log, commit, or add API keys, tokens, environment values, or shell tickets to source files, command output, or repository configuration.
Inspect authentication and project state before changing anything. Check the command exit code and query resulting state; a submitted request is not proof of success.
Run pull --dry-run or push --dry-run before changing a local workspace, then inspect repository instructions and local changes.
Treat preview and production as separate environments. A production release requires an interactive TTY and explicit user confirmation; do not attempt or imply a non-interactive production release.
If a deployment fails or times out, preserve its deployment/release ID and use deploy status or deploy history rather than blindly retrying.

Authenticate and discover

d1v auth status --format json
d1v project list --format json
d1v github status --format json

If authentication is missing, ask the user to run d1v auth login. Do not ask them to paste a token into chat or a command line. An API key supplied through a secure standard-input workflow can be used with d1v auth login --api-key.

Bind a local workspace

d1v project get <project_id> --format json
d1v init . --project-id <project_id>
d1v pull --dry-run --format json
d1v pull
d1v push --dry-run --format json
d1v push

d1v init writes local workspace metadata. Do not use --force unless the user explicitly approves replacing an existing binding.

Run commands in a workspace

Use an interactive shell only when a person needs a terminal:

d1v shell
d1v shell <project_id>
d1v shell --organization-id <organization_id>

With no target, d1v shell opens the personal workspace root.
A project ID opens that project's directory. Do not combine it with --organization-id.
Interactive shells require a TTY and text output. Do not use --format json with d1v shell.

Read the full file on GitHub · 135 lines

Changes

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 First seen · 135 lines · 57 tokens per session scan A 3a8e45ec42f1

Subscribe to this mod's changes

d1v is a skill published in the GitHub repository d1vai/d1v-cli (25 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 1,238 once invoked, about $0.0002 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.

Containers DevOps and cloud

deploy-docker-compose

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…

omnigent-ai/omnigent · 84 tokens

bdd-container-update

Update the BDD test container image when its dependencies or runtime change. Determines version bump (major vs minor vs patch), rebuilds the Docker image, pushes to GitLab registry, and updates the image tag in starttest.sh. Test source (tests/, features/, scripts/, data/, conftest.py) is bind-mounted from the host…

NVIDIA-AI-Blueprints/video-search-and-summarization · 117 tokens

securing-kubernetes-on-cloud

This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…

xalgorix/xalgorix · 80 tokens

d1v