Borrowing it
Nothing to install: this file belongs to salesforce-ux/design-system-2-starter-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/salesforce-ux/design-system-2-starter-kit/main/.agent/skills/first-time-deploy/SKILL.mdgit clone --depth 1 https://github.com/salesforce-ux/design-system-2-starter-kitWrote 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/salesforce-ux/design-system-2-starter-kit/first-time-deploy)<a href="https://agentmods.dev/skills/salesforce-ux/design-system-2-starter-kit/first-time-deploy"><img src="https://agentmods.dev/badge/skills/salesforce-ux/design-system-2-starter-kit/first-time-deploy/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.
<a href="https://agentmods.dev/skills/salesforce-ux/design-system-2-starter-kit/first-time-deploy"><img src="https://agentmods.dev/badge/skills/salesforce-ux/design-system-2-starter-kit/first-time-deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Agent Snooping · line 19 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00066 | $0.00608 |
| Opus 5 | $0.00033 | $0.00304 |
| Sonnet 5 | $0.00013 | $0.00122 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
first-time-deploy 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 9d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy to GitHub Pages
For repeat deploys, run npm run deploy. That's it.
The steps below cover first-time setup: ensuring a repo exists, deploying, and configuring GitHub Pages.
Tone
Important: The user may not be technical. Always use the correct technical term but immediately follow it with a plain-language explanation in parentheses, e.g. "deploy your site (build and publish it so others can visit the link)" or "configure Pages (tell GitHub which branch to serve as a website)". Do this every time, not just the first mention.
Prerequisites
Run the repo-setup skill first (.agent/skills/repo-setup/SKILL.md). It handles brew, gh CLI, authentication, repo creation, and initial push. It also detects the GitHub <hostname> from the origin remote. Use that same <hostname> throughout the steps below.
Steps
1. Deploy (creates gh-pages branch)
Run the project's deploy script. This builds the site with hash routing and pushes dist/ to the gh-pages branch:
npm run deploy
This must happen before configuring Pages settings, because the gh-pages branch must exist first.
2. Configure GitHub Pages on the repo
After gh-pages exists on the remote, configure the repo:
gh api repos/{owner}/{repo}/pages \
--hostname <hostname> \
--method POST \
--field source='{"branch":"gh-pages","path":"/"}' \
--silent 2>/dev/null \
|| gh api repos/{owner}/{repo}/pages \
--hostname <hostname> \
--method PUT \
--field source='{"branch":"gh-pages","path":"/"}'
The POST creates the Pages config; if it already exists the PUT updates it.
Verify:
gh api repos/{owner}/{repo}/pages --hostname <hostname> --jq '.source'
Expected: { "branch": "gh-pages", "path": "/" }.
3. Get the deployed URL
gh api repos/{owner}/{repo}/pages --hostname <hostname> --jq '.html_url'
Share the URL with the user. If the API does not return a URL (Pages may still be provisioning), tell the user they can find it under Settings > Pages on the repo.
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.
- 9d ago First seen · 66 lines · 66 tokens per session scan A ddc20c167a24
first-time-deploy is a skill published in the GitHub repository salesforce-ux/design-system-2-starter-kit (23 stars, last pushed 18d ago), licensed Apache-2.0. It adds 66 tokens to every session and 608 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…