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/d1vai/d1v-cli/d1vnpx skills add d1vai/d1v-cli --skill d1vgit clone --depth 1 https://github.com/d1vai/d1v-cliWhat 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.00057 | $0.01238 |
| Opus 5 | $0.00028 | $0.00619 |
| Sonnet 5 | $0.00011 | $0.00248 |
| Haiku 4.5 | $0.00006 | $0.00124 |
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 3d 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 — 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-runorpush --dry-runbefore 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 statusordeploy historyrather 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 shellopens 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 jsonwithd1v shell.
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.
- 3d ago First seen · 135 lines · 57 tokens per session scan A 3a8e45ec42f1
d1v is a skill published in the GitHub repository d1vai/d1v-cli (23 stars, last pushed 4d ago), licensed MIT. It adds 57 tokens to every session and 1,238 once invoked, about $0.0003 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
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).
openshell-cli
Guide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, policy iteration, settings, service exposure, BYOC workflows, and inference routing. Covers basic through advanced multi-step workflows. Trigger keywords - openshell, sandbox…
cloud-k8s
Use for authorized cloud, container, and Kubernetes security assessment including metadata SSRF, IAM misconfig, container escape paths, and cluster RBAC review.
kubernetes-specialist
Use when deploying or managing Kubernetes workloads. Invoke to create deployment manifests, configure pod security policies, set up service accounts, define network isolation rules, debug pod crashes, analyze resource limits, inspect container logs, or right-size workloads. Use for Helm charts, RBAC policies…
langbot-deploy
Deploy and configure a LangBot instance — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key. Use when installing, deploying, upgrading, or configuring LangBot in production or self-hosted environments. Triggers on "deploy langbot", "langbot…
doca-container-deployment
Use this skill when the user is hands-on deploying an in-bundle DOCA service container (Argus, DMS, Firefly, or UROM service) on a BlueField — kubelet standalone watching a static-pod manifests directory, YAML pod-spec drop, kubelet status / ENTRYPOINT logs / per-service liveness, smoke-before-bulk, and the layered…