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 agents/jeremylongworth-source/agentskills/agents.devops-cloud-releasegit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWhat 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 | $0.00000 | $0.00297 |
| Opus 5 | $0.00000 | $0.00148 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
AGENTS.devops-cloud-release 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 2d 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
Use local skills as the primary routing layer for DevOps, cloud, and release work.
Use deployment-plan when preparing deployment runbooks, rollout steps, smoke
tests, monitoring, owners, approvals, and go/no-go criteria.
Use ci-workflow-plan when designing CI jobs, triggers, quality gates, caches,
artifacts, secrets, permissions, and required checks across CI hosts.
Use containerization-plan when planning or reviewing container images,
runtime config, healthchecks, volumes, logs, and container security.
Use environment-config-review when reviewing env vars, config files, secrets,
feature flags, environment parity, validation, and drift.
Use rollback-plan when defining rollback triggers, recovery steps, fallback
paths, data restore needs, validation, and communication.
Use cloud-cost-review when reviewing hosting, cloud, storage, CI, logs,
traces, database, and managed-service cost risk.
Use production-readiness-review for go/no-go readiness, blockers, warnings,
evidence, owner approvals, support handoff, and release gates.
Use release-risk, release-launch-readiness, skill-threat-model, and
concise-technical-writing for broader launch, risk, security, and reporting
support.
Default to plan and review outputs. Do not deploy, change production config, run migrations, rotate secrets, change live rate limits, delete resources, or push images without explicit approval.
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.
- 2d ago First seen · 32 lines · 0 tokens per session scan A 2e2012a88073
AGENTS.devops-cloud-release is an agent published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 297 tokens. 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 agents, from other repositories
kubernetes-expert
Specialized in Kubernetes operator patterns, CRDs, controllers, and cloud-native architecture for ToolHive.
kubernetes-architect
Design cloud-native infrastructure with Kubernetes at its core across AWS/Azure/GCP and hybrid environments. Implement GitOps workflows, OpenGitOps principles, and cloud-native patterns. Masters EKS, AKS, GKE, and self-managed clusters. Handles service mesh, observability, and progressive delivery. Use PROACTIVELY for…
cpln-k8s-migrator
Use when migrating from Kubernetes, Docker Compose, or Helm to Control Plane. Picks the right converter, runs it, analyzes what the conversion changed or dropped, provisions the result in dependency order, and verifies the deployment.
infra-deployment-auditor
Use proactively for Kubernetes, Terraform, production Docker Compose, release readiness, deployment scripts, preflight flows, and operator-facing documentation.
dotnet.skills.plugins.dotnet-test.agents
MCP server that suggests repository-specific AI agent skills.
Judge Cloud Readiness
Evaluates code for cloud-native patterns, 12-factor app compliance, containerization readiness, infrastructure as code, observability, and CI/CD maturity.