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/stbenjam/skillsaw/deploy-servicenpx skills add stbenjam/skillsaw --skill deploy-servicegit clone --depth 1 https://github.com/stbenjam/skillsawWrote 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/stbenjam/skillsaw/deploy-service)<a href="https://agentmods.dev/skills/stbenjam/skillsaw/deploy-service"><img src="https://agentmods.dev/badge/skills/stbenjam/skillsaw/deploy-service.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.00018 | $0.00451 |
| Opus 5 | $0.00009 | $0.00226 |
| Sonnet 5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
deploy-service 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 6d 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.
What it actually says
Deploy Service
Automates the deployment of microservices to Kubernetes clusters using Helm charts and environment-specific value overrides.
When to Use This Skill
Use when deploying a service to staging or production, or when updating an existing deployment with new configuration.
Implementation Steps
Step 1: Validate Chart
Run helm lint charts/ to verify the Helm chart is syntactically valid.
Check that all required values are defined in values.yaml:
image.repositoryimage.tagreplicaCountresources.limits.cpuresources.limits.memory
Step 2: Apply Configuration
Merge environment-specific values from values-{env}.yaml with the
base values.yaml file:
helm template my-service charts/ \
-f charts/values.yaml \
-f charts/values-$ENV.yaml \
--dry-run
Review the rendered manifest before applying.
Step 3: Execute Deployment
Run helm upgrade --install with the merged configuration:
helm upgrade --install my-service charts/ \
-f charts/values.yaml \
-f charts/values-$ENV.yaml \
-n $NAMESPACE \
--wait --timeout 300s
Step 4: Verify
Run kubectl rollout status deployment/my-service -n $NAMESPACE to
confirm all pods are ready. Check that health endpoints return 200.
Examples
Example 1: Deploy to Staging
Deploy the user service to the staging cluster with default values:
helm upgrade --install user-service charts/ -f charts/values-staging.yaml -n staging
Example 2: Deploy with Custom Tag
Override the image tag for a specific build:
helm upgrade --install user-service charts/ --set image.tag=abc1234 -n production
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.
- 6d ago First seen · 76 lines · 18 tokens per session scan A bfb23d9298b4
deploy-service is a skill published in the GitHub repository stbenjam/skillsaw (62 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 451 once invoked, about $0.0001 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
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…
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…
compute-env-setup
Set up a compute environment on a remote provider so Claude Science jobs can run there. Covers direct SSH/conda hosts, Slurm clusters, container-via-bridge runners, and managed-API providers (Modal, GCP, RunPod). Use when standing up a new provider, porting an env to a different backend, adding a tool that needs its…
azure-cloud-migrate
Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
atmos-helmfile
Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management.