deploy-verify

deploy-verify is a skill for Claude Code, Codex from chipi/agentic-ai-homelab. It costs 136 tokens per session (1,386 once invoked), scanned A, original, MIT.

A deployment check that compares service telemetry before and after a release. Telemetry is operational data such as logs, traces, metrics, and error reports.

In plain words
What is it for?
It helps snapshot and compare service signals, confirm the deployed release appears in traces, check metric collection, list new GlitchTip errors, and review flagged results.
Why use it?
It catches missing production logs, traces, metrics, or newly reported errors after deployment instead of relying on the application merely starting.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths.

Good fit It helps snapshot and compare service signals, confirm the deployed release appears in traces, check metric collection, list new GlitchTip errors, and review flagged results.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chipi/agentic-ai-homelab/deploy-verify
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 chipi/agentic-ai-homelab --skill deploy-verify
Clone the repo
git clone --depth 1 https://github.com/chipi/agentic-ai-homelab

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 deploy-verify

README.md
[![agentmods](https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/deploy-verify/github.svg)](https://agentmods.dev/skills/chipi/agentic-ai-homelab/deploy-verify)
Your own site
<a href="https://agentmods.dev/skills/chipi/agentic-ai-homelab/deploy-verify"><img src="https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/deploy-verify/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 deploy-verify

Your own site · 80×15
<a href="https://agentmods.dev/skills/chipi/agentic-ai-homelab/deploy-verify"><img src="https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/deploy-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 136 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,386 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.
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.00136 $0.01386
Opus 5.5 $0.00054 $0.00554
Sonnet 5.5 $0.00027 $0.00277
Haiku 4.5 $0.00014 $0.00139

Measured yesterday against content hash f55e455515f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deploy-verify 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 yesterday.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/verify.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

workstation/claude/skills/deploy-verify/SKILL.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

deploy-verify

After every deploy on 2026-10-16/17, someone wrote a fresh verify script per service by hand. This is that script, once, for both projects. It is a gate: expected against live, PASS/FAIL. o11y-review is a review: patterns and counts over a window. Use both:

  • the gate first;
  • then o11y-review for anything the gate flags.

Run (on the mini, through host-run)

V=~/.claude/skills/deploy-verify/scripts/verify.py
R=~/.claude/skills/host-run/scripts/run.sh

$R homelab $V snapshot --project closelistening --out /tmp/cl-base.json     # before the deploy
# ...deploy, then let it serve traffic for a while (10+ minutes)...
$R homelab $V compare --project closelistening --baseline /tmp/cl-base.json --release sha-ded80e0
$R homelab $V compare --project orrery --since 2026-10-17T08:21:00Z --sourcemaps
  • Projects: closelistening and orrery. The PROFILES table in the script lists each one's services, scrape jobs, counters, GlitchTip projects, Langfuse key file, Umami sites and live URL. Add a project there.
  • --since: use it when there is no baseline, i.e. the time the new version went live.
  • --release: the image tag the deploy shipped (sha-<7>, ADR-0010).
    • For podcast, run from the deploy's image tag, not the workflow commit. On 2026-10-16 deploy-all ran from b0edbb9 and deployed sha-ded80e0.
    • orrery's web release is gha-<short sha> and isn't checked by this flag.
Check PASS means
logs each service has prod lines since the deploy. Non-prod lines (dev runs) are INFO; lines with no environment label FAIL.
traces each traced service has traces since the deploy, and service.version includes --release
metrics every scrape job up=1; every listed counter has series over 2 days (count_over_time, not an instant query)
errors no GlitchTip issue first seen since the deploy. Each new one FAILs the gate on purpose: someone has to look. Its status is shown.
langfuse app traces since the deploy all carry --release. LiteLLM's own litellm-* traces are ignored.
umami each site got events since the deploy, with the latest event's time. Zero events is INCONCLUSIVE while the time since the deploy is shorter than the quiet gap before it, from the site's last event to the deploy (sparse traffic: re-run compare later), and WARN once it is older. A failed Umami query is a FAIL, not "0 events"
sourcemaps every live _app/immutable JS with a debugId has a stored GlitchTip bundle. Unmatched stubs under 1 KB are INFO.

Read the full file on GitHub · 80 lines

Files

What ships with it

2 files 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. yesterday Changed · +9 lines f55e455515f8
  2. 7d ago Changed e6bdb43b1ed2
  3. 17d ago First seen · 71 lines · 136 tokens per session scan A bbdf01737d01

Subscribe to this mod's changes

deploy-verify is a skill published in the GitHub repository chipi/agentic-ai-homelab (3 stars, last pushed today), licensed MIT. It adds 136 tokens to every session and 1,386 once invoked, about $0.0005 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-10-18.