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 joonlab/joonlab-claudecode-setting-for-share --skill netlify-deploygit clone --depth 1 https://github.com/joonlab/joonlab-claudecode-setting-for-shareWrote 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/joonlab/joonlab-claudecode-setting-for-share/netlify-deploy)<a href="https://agentmods.dev/skills/joonlab/joonlab-claudecode-setting-for-share/netlify-deploy"><img src="https://agentmods.dev/badge/skills/joonlab/joonlab-claudecode-setting-for-share/netlify-deploy.svg" alt="Measured on agentmods" height="20"></a>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.00073 | $0.00921 |
| Opus 5 | $0.00036 | $0.00461 |
| Sonnet 5 | $0.00015 | $0.00184 |
| Haiku 4.5 | $0.00007 | $0.00092 |
Grade A, and why
netlify-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 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Netlify Deploy
Overview
Deploy web projects to Netlify using the Netlify CLI. Supports static HTML sites, React/Vue/Next.js builds, and any web project. Handles both new site creation and updates to existing sites.
Credentials
Credentials are stored in references/credentials.md. Read this file to get the access token and account slug before any deployment operation.
Deployment Workflow
Step 1: Verify Netlify CLI Installation
which netlify || npm install -g netlify-cli
Step 2: Analyze Project Structure
Before deployment, analyze the project folder to determine:
- Static HTML site: Contains
index.htmlat root → deploy root folder (.) - React/Vue (Vite): Contains
package.jsonwith vite → build output isdist/ - Create React App: Contains
package.jsonwith react-scripts → build output isbuild/ - Next.js static export: Contains
next.config.js→ build output isout/ - Custom build: Check
package.jsonfor build script and output directory
For projects requiring build:
cd <project-folder> && npm install && npm run build
Step 3: Create New Site (if needed)
To create a new site with a specific name:
NETLIFY_AUTH_TOKEN="<token>" netlify sites:create --name "<site-name>" --account-slug "<account-slug>" --disable-linking
The output provides:
- Site URL:
https://<site-name>.netlify.app - Site ID: Used for subsequent deployments
Step 4: Deploy
For production deployment:
cd <project-folder> && NETLIFY_AUTH_TOKEN="<token>" netlify deploy --prod --dir=<output-dir> --site="<site-id>"
Parameters:
--prod: Deploy to production (main URL)--dir: Build output directory (.,dist,build, etc.)--site: Site ID from creation step or existing site
Step 5: Verify and Report
After successful deployment, report:
- Production URL:
https://<site-name>.netlify.app - Admin URL:
https://app.netlify.com/projects/<site-name>
Common Operations
What ships with it
1 file 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.
- 8d ago First seen · 120 lines · 73 tokens per session scan A b1d9f67ef0c6
netlify-deploy is a skill published in the GitHub repository joonlab/joonlab-claudecode-setting-for-share (10 stars, last pushed 29d ago), licensed MIT. It adds 73 tokens to every session and 921 once invoked, about $0.0004 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-31.
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…