Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add pwdev-solucoes/pwdev-claude-marketplace/plugin install pwdev-devopsWrote 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/pwdev-solucoes/pwdev-claude-marketplace/devops-context)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/devops-context"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/devops-context.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.00100 | $0.00607 |
| Opus 5 | $0.00050 | $0.00303 |
| Sonnet 5 | $0.00020 | $0.00121 |
| Haiku 4.5 | $0.00010 | $0.00061 |
Grade A, and why
devops-context 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
Contexto da Plataforma
Você levanta o inventário uma vez para que nenhuma skill precise adivinhar depois.
Princípio central
A pergunta mais perigosa em DevOps é "isso é produção?". Este arquivo existe para que ela nunca precise ser respondida por palpite.
Passo 1 — Estado
Existe: leia, resuma, pergunte o que atualizar. Não existe: copie o template.
Passo 2 — Mapeamento de ambiente (resolva primeiro)
O bloco mais importante. Sem ele, toda operação é tratada como produção.
| Ambiente | Conta AWS | Contexto kubectl | Host | Banco |
| prod | 1234... | arn:...prod | ... | ... |
| staging | 5678... | arn:...stg | ... | ... |
Colete de fato, não de memória:
aws sts get-caller-identitypor perfilkubectl config get-contexts
Nome contendo "prod" não é evidência suficiente. Exija o identificador real.
Passo 3 — Inventário
Contas e perfis · clusters e nodegroups · bancos com versão e tamanho · hosts e função · domínios e certificados · repositórios e pipelines · janela de manutenção · quem é dono do quê.
Passo 4 — Operação
- Quem aprova mudança em produção
- Canal de incidente
- Onde vivem os runbooks
- SLO por serviço, se existir
- Retenção e local dos backups
Passo 5 — Ferramentas
Rode ${CLAUDE_PLUGIN_ROOT}/scripts/check-tools.sh e registre.
Ferramenta ausente = skill em modo consultivo.
Nunca grave credencial, token ou senha neste arquivo. Registre o local do segredo (Secrets Manager, Vault, SSM), nunca o valor.
Limites
- Não executa mudança na infra
- Não armazena segredo, em nenhuma hipótese
- Não infere ambiente por nome de recurso
- Não substitui o inventário oficial — complementa
Skills relacionadas
platform-docs · todas as demais consomem este arquivo
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 · 68 lines · 100 tokens per session scan A 20db91ecc88b
devops-context is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 17d ago), licensed Apache-2.0. It adds 100 tokens to every session and 607 once invoked, about $0.0005 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-09-03.
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…