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 skills/lantisprime/claude-sdlc/supportnpx skills add lantisprime/claude-sdlc --skill supportgit clone --depth 1 https://github.com/lantisprime/claude-sdlcWrote 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/lantisprime/claude-sdlc/support)<a href="https://agentmods.dev/skills/lantisprime/claude-sdlc/support"><img src="https://agentmods.dev/badge/skills/lantisprime/claude-sdlc/support.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 | $0.00100 | $0.00746 |
| Opus 5 | $0.00050 | $0.00373 |
| Sonnet 5 | $0.00020 | $0.00149 |
| Haiku 4.5 | $0.00010 | $0.00075 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Support (Phase 7)
Make the change observable in production.
Prerequisite
.claude/sdlc/gates/deploy-<task-slug>.md must exist and be signed.
Step 1 — Identify what to watch
From the plan's in-scope surface and the security/NFR sections of the architecture, enumerate:
- New code paths → structured log events at key decision points
- New endpoints or RPCs → request count, error rate, latency (p50/p95/p99)
- New background jobs → run count, duration, failure rate
- New external calls → timeout, failure, retry counters
- New failure modes from the threat model → alerts
For each, write: what to measure, why, threshold for alert, who is paged, runbook link.
Step 2 — Produce artifacts
Write to .claude/sdlc/monitoring/<task-slug>/:
- Logging changes — code deltas (in a follow-up PR, not this build's PR) or config changes
- Metrics — platform-appropriate config (Prometheus rules, Datadog monitors, CloudWatch alarms)
- Dashboards — JSON or TOML for the configured platform; a README if none is configured
- Alerts — with routing (oncall rotation / channel), severity, auto-resolve conditions
- Runbook stub —
runbook.mdwith symptom → diagnostic → mitigation
Step 3 — Integrate (when configured)
If an observability platform is configured in .claude/sdlc/env.json:
- Grafana/Datadog via MCP → propose dashboard and alert changes as pull requests or API calls; never auto-apply production alert changes without human confirmation
- CloudWatch → propose IaC changes
Never silently mutate production monitoring.
Step 4 — Validate
- Generate a synthetic failure in a non-production environment and confirm the alert fires.
- Confirm the runbook entry matches what an on-call engineer would need at 3am.
Human gate
Summarize: what's now being watched, what's alerted, runbook status. Sign-off → .claude/sdlc/gates/support-<task-slug>.md.
What this skill must NOT do
- Do not auto-apply changes to production alerting.
- Do not skip a runbook entry ("we'll document later" is how silent outages happen).
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.
- 3d ago First seen · 77 lines · 100 tokens per session scan A c86602e3feea
support is a skill published in the GitHub repository lantisprime/claude-sdlc (3 stars, last pushed 4mo ago), licensed MIT. It adds 100 tokens to every session and 746 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-08-31.
Other skills, from other repositories
weather-fetcher
Instructions for fetching current weather temperature data for Dubai, UAE from Open-Meteo API.
clinpgx-database
Access ClinPGx pharmacogenomics data (successor to PharmGKB). Query gene-drug interactions, CPIC guidelines, allele functions, for precision medicine and genotype-guided dosing decisions.
embedding-strategies
Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific domains.
datavis
Comprehensive data visualization toolkit for creating beautiful, mathematically elegant visualizations with D3.js, Chart.js, and custom SVG. Use when (1) building interactive data visualizations, (2) designing color palettes for charts, (3) choosing scales and visual encodings, (4) creating data pipelines from…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
detecting-data-anomalies
Investigate outliers, rare events, spikes, and suspicious records in datasets. Use as an explicit anomaly-analysis helper when you want concrete anomaly-detection workflow guidance, not generic data validation or end-to-end ML ownership.