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 G1Joshi/Agent-Skills --skill nomadgit clone --depth 1 https://github.com/G1Joshi/Agent-SkillsWrote 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/g1joshi/agent-skills/nomad)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/nomad"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/nomad/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/g1joshi/agent-skills/nomad"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/nomad.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.01314 |
| Opus 5.5 | $0.00018 | $0.00526 |
| Sonnet 5.5 | $0.00009 | $0.00263 |
| Haiku 4.5 | $0.00004 | $0.00131 |
Grade A, and why
nomad 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 24d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nomad
HashiCorp Nomad is a lightweight, flexible workload orchestrator capable of managing containerized, non-containerized, and virtualized applications across bare metal and multi-cloud environments.
When to Use
- Simple & Flexible Workload Orchestration: Deploying containers, non-containerized binaries, and batch jobs across clouds and bare metal.
- Lightweight Alternative to Kubernetes: Single-binary cluster management with significantly lower operational complexity.
- HashiCorp Ecosystem Integration: Native interoperability with Consul (service discovery) and Vault (secret management).
- Hybrid Multi-Region Workloads: Scheduling Windows and Linux jobs seamlessly across distributed datacenters.
Quick Start
job "example" {
datacenters = ["dc1"]
group "cache" {
task "redis" {
driver = "docker"
config {
image = "redis:7"
}
resources {
cpu = 500 # 500 MHz
memory = 256 # 256 MB
}
}
}
}
Core Concepts
Production Job Specification (job.nomad)
Deploying a containerized service with Consul and Vault:
job "api-service" {
datacenters = ["dc1"]
type = "service"
group "web" {
count = 3
update {
max_parallel = 1
min_healthy_time = "30s"
healthy_deadline = "3m"
auto_revert = true # Automatic rollback on deployment failure
}
network {
port "http" {
to = 8080
}
}
service {
name = "api-service"
port = "http"
provider = "consul"
check {
type = "http"
path = "/healthz"
interval = "10s"
timeout = "2s"
}
}
task "server" {
driver = "docker"
config {
image = "registry.example.com/api-service:v2.1.0"
ports = ["http"]
}
resources {
cpu = 500 # MHz
memory = 512 # MB
}
vault {
policies = ["api-service-policy"]
}
template {
data = "DATABASE_URL={{ with secret \"secret/data/db\" }}{{ .Data.data.url }}{{ end }}"
destination = "secrets/file.env"
env = true
}
}
}
}
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.
- 24d ago Changed · +5 lines e6b5b054491f
- 28d ago Changed · +151 lines · +27 tokens per session be3c05a1a149
- 1mo ago First seen · 68 lines · 17 tokens per session scan A 2334e8f6c310
nomad is a skill published in the GitHub repository G1Joshi/Agent-Skills (15 stars, last pushed 24d ago), licensed MIT. It adds 44 tokens to every session and 1,314 once invoked, about $0.0002 per session on Opus 5.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-03.
Other skills, from other repositories
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
agents-v2-py
Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.
k8s-manifests
Provides production Kubernetes deployment, HPA, and PodDisruptionBudget templates; use when writing Kubernetes YAML, designing Helm charts, setting resource limits, configuring probes, or reviewing pod security.
odoo-docker-deployment
Production-ready Docker and docker-compose setup for Odoo with PostgreSQL, persistent volumes, environment-based configuration, and Nginx reverse proxy.
service-mesh
Implement service mesh for mTLS, traffic management, and observability — Istio and Linkerd patterns for Kubernetes.
cost-optimization
Guides systematic cloud and infrastructure cost reduction. Use when cloud bills are growing unpredictably, when rightsizing resources, when evaluating reserved capacity, or when building cost-aware architecture. Use when you need to optimize spend without sacrificing reliability or performance.