check-deployment-status

check-deployment-status is a skill for Claude Code, Codex from caipe-io/ai-platform-engineering. It costs 54 tokens per session (626 once invoked), scanned A, original, Apache-2.0.

A status report for applications managed by ArgoCD across clusters. ArgoCD is a deployment tool that keeps running applications aligned with their declared configuration.

In plain words
What is it for?
Use it to monitor application health, verify deployments after releases, investigate sync failures, inspect failing resources, and decide whether to sync, roll back, or adjust configuration.
Why use it?
It reveals deployments that are out of sync, degraded, missing, or otherwise unhealthy, so teams can investigate release problems quickly.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to monitor application health, verify deployments after releases, investigate sync failures, inspect failing resources, and decide whether to sync, roll back, or adjust configuration.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/caipe-io/ai-platform-engineering/check-deployment-status
Install

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.

Any agent
npx skills add caipe-io/ai-platform-engineering --skill check-deployment-status
Clone the repo
git clone --depth 1 https://github.com/caipe-io/ai-platform-engineering

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for check-deployment-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/check-deployment-status/github.svg)](https://agentmods.dev/skills/caipe-io/ai-platform-engineering/check-deployment-status)
Your own site
<a href="https://agentmods.dev/skills/caipe-io/ai-platform-engineering/check-deployment-status"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/check-deployment-status/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.

agentmods 80×15 button for check-deployment-status

Your own site · 80×15
<a href="https://agentmods.dev/skills/caipe-io/ai-platform-engineering/check-deployment-status"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/check-deployment-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 626 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.00626
Opus 5 $0.00027 $0.00313
Sonnet 5 $0.00011 $0.00125
Haiku 4.5 $0.00005 $0.00063

Measured 10d ago against content hash 3f4f3b3ca9ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

check-deployment-status 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 10d 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.

charts/ai-platform-engineering/data/skills/check-deployment-status/SKILL.md · 61 lines

What it actually says

Check Deployment Status

Retrieve and analyze the current state of all ArgoCD-managed applications. Surface any that are `OutOfSync`, `Degraded`, `Missing`, or `Unknown`, and provide clear next steps.

Instructions

  1. List all ArgoCD applications using the ArgoCD agent's MCP tools. Request application name, project, sync status, health status, and target revision.
  2. Categorize results into:
    • Healthy & Synced - no action needed
    • OutOfSync - drift detected between desired and live state
    • Degraded / Unhealthy - runtime health issues (crashloops, pending pods, failed probes)
    • Missing / Unknown - application or resources cannot be found
  3. For each unhealthy application, provide:
    • Application name and namespace
    • Current sync and health status
    • Last sync timestamp and result
    • Resource-level details (which pods/deployments are failing)
    • Suggested remediation (sync, rollback, check resource limits, etc.)
  4. Summary table at the top with total counts per status category.

Output Format

```markdown

Deployment Status Summary

Status Count
Healthy 42
OutOfSync 3
Degraded 1
Missing 0

Issues Requiring Attention

1. my-app (namespace: production)
  • Sync Status: OutOfSync
  • Health: Degraded
  • Last Sync: 2026-02-08T14:23:00Z (Failed)
  • Details: Deployment `my-app` has 0/3 ready replicas. Pod `my-app-7d4b8c` in CrashLoopBackOff.
  • Recommended Action: Check container logs for startup errors. Verify resource limits and environment variables. ```

Examples

  • "Show me the status of all ArgoCD applications"
  • "Are there any deployments that are out of sync?"
  • "Check deployment health after the last release"
  • "Which applications are degraded in the staging cluster?"

Guidelines

  • Always paginate results (default page size: 20) to avoid OOM with large application counts
  • Group results by project or cluster when there are more than 50 applications
  • Highlight time since last successful sync for OutOfSync apps
  • If all applications are healthy, confirm with a brief positive summary rather than listing every app
  • When degraded apps are found, check for recent deployment events that may correlate
Files

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.

Changes

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.

  1. 10d ago First seen · 61 lines · 54 tokens per session scan A 3f4f3b3ca9ec

Subscribe to this mod's changes

check-deployment-status is a skill published in the GitHub repository caipe-io/ai-platform-engineering (407 stars, last pushed yesterday), licensed Apache-2.0. It adds 54 tokens to every session and 626 once invoked, about $0.0003 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.