support

A command for the support phase after a deployment, covering monitoring, logs, alerts, dashboards, and a runbook. A runbook is a written guide for responding to operational problems.

In plain words
What is it for?
Use it to produce logging changes, metrics and alert configuration, dashboard data, and a runbook stub, with a sign-off record after completion.
Why use it?
It helps turn a deployed change into something that can be observed and supported when failures occur.

Command

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.

agentmods
npx agentmods add commands/lantisprime/claude-sdlc/support
Clone the repo
git clone --depth 1 https://github.com/lantisprime/claude-sdlc
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 152 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00024 $0.00152
Opus 5 $0.00012 $0.00076
Sonnet 5 $0.00005 $0.00030
Haiku 4.5 $0.00002 $0.00015

Measured 2d ago against content hash e8575cf66a69, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

commands/support.md · 12 lines

What it actually says

Invoke the support skill. Prerequisite: .claude/sdlc/gates/deploy-<task-slug>.md.

Produces platform-neutral artifacts when no observability platform is configured. Integrates via MCP when Grafana/Datadog/CloudWatch is wired up — but never auto-applies production alert changes.

Produces: logging deltas, metrics/alert config, dashboard JSON, runbook stub.

On completion, invoke the gate-signoff skill to capture the human sign-off via chat and write .claude/sdlc/gates/support-<task-slug>.md.

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. 2d ago First seen · 12 lines · 24 tokens per session scan A e8575cf66a69

Subscribe to this mod's changes

support is a command published in the GitHub repository lantisprime/claude-sdlc (3 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 152 once invoked, about $0.0001 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-31.