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 VincentChuWaiChow/vanguard-frontier-agentic --skill databricks-developer-platformgit clone --depth 1 https://github.com/VincentChuWaiChow/vanguard-frontier-agenticWrote 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/vincentchuwaichow/vanguard-frontier-agentic/databricks-developer-platform)<a href="https://agentmods.dev/skills/vincentchuwaichow/vanguard-frontier-agentic/databricks-developer-platform"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/databricks-developer-platform.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 60 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 71 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 101 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 61 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00092 | $0.03426 |
| Opus 5 | $0.00046 | $0.01713 |
| Sonnet 5 | $0.00018 | $0.00685 |
| Haiku 4.5 | $0.00009 | $0.00343 |
Grade A, and why
databricks-developer-platform 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 4d 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.
databricks-developer-platform
Purpose
This skill decides whether a bundle's configuration and deployment machinery are safe for the stated target. A bundle is production-ready only when the target is narrowly scoped, deployment modes are correctly wired to their semantics, run-as identity is minimally privileged and correctly gated, variables are resolved at deployment time only, authentication is OAuth or environment-based rather than persisted-token based, the Git folder flow segregates admin and user branches, and every CI/CD gate is written to prevent accidental environment promotion. A bundle that passes structure but has weak authentication or mixed Git folders is pass-with-conditions at best.
When to use
- A user provides a
databricks.ymlbundle configuration and asks whether it is safe to deploy to production or a higher environment. - A user is setting up a bundle deployment pipeline and wants to verify that targets, deployment modes, and promotion gates are correctly wired.
- A user is designing run-as identity or authentication for a bundle deployment and wants to confirm the design is coherent with the deployment scope.
- A user is implementing a Git folder flow or CI/CD gate for bundle promotion and needs to verify that the flow prevents accidental environment crossing.
When NOT to use
- No bundle configuration is provided — ask for the
databricks.ymlfile rather than guessing. - The request is to actually deploy or mutate the live workspace — that is the live-guard gate with explicit approval, not a review scope.
- The concern is identity governance or secret rotation — route to
databricks-identity-network-security-agent. - The concern is pipeline execution or job scheduling — route to
databricks-lakeflow-pipeline-engineering-agent. - The concern is runtime reliability or incident diagnosis — route to
databricks-platform-reliability-agent.
Scope
- Bundle configuration validation: one
databricks.yml, top-level keys, resource types, and deployment-mode alignment. - Run-as identity design: principal constraints, non-admin boundaries, resource-type incompatibilities.
- Variable resolution: deployment-time only, precedence order, supported lookups, and no runtime availability.
- Authentication: OAuth U2M/M2M, environment variables, token storage, CLI version, and credential exposure.
- Git folder flows: admin/user/merge segregation, branch protection, and promotion gates.
- CI/CD gate design: environment-crossing prevention, approval workflows, and rollback readiness.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 135 lines · 92 tokens per session scan A c9e368906aac
databricks-developer-platform is a skill published in the GitHub repository VincentChuWaiChow/vanguard-frontier-agentic (22 stars, last pushed today), licensed Apache-2.0. It adds 92 tokens to every session and 3,426 once invoked, about $0.0005 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-09-04.
Other skills, from other repositories
usethis
R usethis package for workflow automation. Use for package setup, Git, GitHub, and project configuration.
bio-applied-testing-cicd
Write pytest tests/fixtures for bio functions and GitHub Actions CI with pytest-cov, ruff, black, mypy. Use when adding tests to a bio tool, writing conftest.py fixtures, or building tests.yml/lint.yml CI workflows.
auditing-azure-active-directory-configuration
Auditing Microsoft Entra ID (Azure Active Directory) configuration to identify risky authentication policies, overly permissive role assignments, stale accounts, conditional access gaps, and guest user risks using AzureAD PowerShell, Microsoft Graph API, and ScoutSuite.
analyzing-azure-activity-logs-for-threats
Queries Azure Monitor activity logs and sign-in logs via azure-monitor-query to detect suspicious administrative operations, impossible travel, privilege escalation, and resource modifications. Builds KQL queries for threat hunting in Azure environments. Use when investigating suspicious Azure tenant activity or…
bioinformatics-workflows-cicd
Build reproducible, resumable bioinformatics pipelines with Snakemake rules or Nextflow DSL2 processes, run nf-core pipelines, and add pytest unit tests plus GitHub Actions CI. Use when writing a Snakefile, defining Nextflow processes/channels, scaling a pipeline to SLURM/AWS/GCP, containerizing tools with…
bun-sveltekit
Use when building or running SvelteKit apps on Bun, including SSR, adapters, and Bun-specific APIs.