agentmods.dev

docs-deployment

A deployment guide for the Qalma documentation website, which is a statically generated site served from Amazon S3 and CloudFront.

In plain words
What is it for?
Use it when working on the docs site's S3 or CDN hosting, infrastructure, caching, domain, TLS certificate, deployment role, or CI deployment workflow.
Why use it?
It explains how the documentation is built, cached, secured, and released so hosting changes follow the project's existing setup.

Skill for Claude CodeCodex

10 1mo ago A scan 107 tokens original MIT
View the source file cdskill/qalma
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 skills/cdskill/qalma/docs-deployment
Any agent
npx skills add cdskill/qalma --skill docs-deployment
Clone the repo
git clone --depth 1 https://github.com/cdskill/qalma

Made for: Claude Code, Codex.

Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,042 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00107 $0.02042
Opus 5 $0.00053 $0.01021
Sonnet 5 $0.00021 $0.00408
Haiku 4.5 $0.00011 $0.00204

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

Security

Grade A, and why

docs-deployment scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -I https://qalma.dev/ # 200, content-encoding: br
.claude/skills/docs-deployment/SKILL.md · 156 lines

How it starts

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

docs-deployment

Infrastructure and delivery for apps/docs (the @qalma/editor docs site). This skill covers hosting and deployment only — not application code.

Hosting model: SSG (not SSR)

apps/docs is built as static site generation — prerendered HTML + hashed assets, no Node server at runtime. Configured in apps/docs/vite.config.ts via the Analog plugin: static: true + prerender (routes + discover) + sitemap host: 'https://qalma.dev/'. Deployable output: dist/apps/docs/analog/public/.

Why SSG over SSR for the docs:

  • Docs content only changes on redeploy → nothing to render per request.
  • SEO is identical to SSR (both ship fully-rendered HTML).
  • Better TTFB/FCP: prerendered HTML served from the CDN edge, no per-request compute.
  • Cheaper and zero ops: no server to run, scale or patch.

Why S3 + CloudFront over Amplify: the build stays in the existing Nx CI (single source of truth, Nx cache) instead of Amplify's own build system, and we get full control of Cache-Control per path — the real lever for FCP/TTFB. Amplify runs CloudFront underneath anyway, so there is no CDN/perf loss.

Architecture

GitHub Actions (nx affected → nx build docs)
        │  assumes IAM role via OIDC (no stored keys)
        ▼
   private S3 bucket  ◀── OAC ──  CloudFront (edge, HTTP/3, Brotli)  ──▶  https://qalma.dev
        ▲                                ▲
   aws s3 sync                    ACM cert (us-east-1) + Route 53 apex alias
   + invalidation

Where things live

  • IaC: infra/terraform/ — providers.tf (AWS + us_east_1 alias for the cert), s3.tf, cloudfront.tf, dns_cert.tf (Route 53 zone as data + ACM + A/AAAA aliases), iam_oidc.tf, variables.tf, outputs.tf, functions/rewrite.js. Human walkthrough: infra/terraform/README.md.
  • CI: .github/workflows/deploy.yml.
  • Deployable artifact: dist/apps/docs/analog/public/.

Infrastructure (Terraform/OpenTofu)

One terraform apply creates ~14 resources:

  • S3: private bucket (block public access on), bucket policy granting read only to this CloudFront distribution via OAC. No website endpoint.
  • CloudFront: distribution with http2and3, compress = true (Brotli/gzip), managed CachingOptimized policy, apex alias, PriceClass_All (global). A CloudFront Function (functions/rewrite.js, viewer-request) maps clean URLs to …/index.html; 403/404 custom_error_response → /index.html (SPA fallback).
  • ACM: DNS-validated cert in us-east-1 (required for CloudFront).
  • Route 53: cert-validation records + apex A/AAAA aliases to CloudFront (hosted zone must already exist; referenced as data).
  • IAM/OIDC: GitHub OIDC provider + least-privilege deploy role (S3 sync + CloudFront invalidation only), trust scoped to repo:cdskill/qalma:ref:refs/heads/main.

Read the full file on GitHub · 156 lines

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 · 156 lines · 107 tokens per session scan A ff893314c77b

Subscribe to this mod's changes

docs-deployment is a skill published in the GitHub repository cdskill/qalma (10 stars, last pushed 1mo ago), licensed MIT. It adds 107 tokens to every session and 2,042 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Data and AIDevOps and cloudWriting and docsangularcontenteditableeditorheadlessprosemirrorrich-text-editor
Related

Other skills, from other repositories

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

heap-snapshot-analysis

Analyze V8 heap snapshots to investigate memory leaks and retention issues. Use when given .heapsnapshot files, asked to compare before/after snapshots, asked to find what retains objects, or investigating why objects survive GC. Provides snapshot parsing, comparison, retainer-path helpers, and scratchpad scripts.

microsoft/vscode · 65 tokens

integrated-browser

Use this when working on the VS Code integrated browser ("browserView") to understand its architecture and mental model. Covers the embedded Chromium browser, its editor tab, navigation, overlay/layout, sessions, and agent browser tools under src/vs/platform/browserView and src/vs/workbench/contrib/browserView.

microsoft/vscode · 68 tokens

tool-rename-deprecation

Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.

microsoft/vscode · 60 tokens

agent-host-e2e-tests

Use when writing, recording, updating, or troubleshooting the agent host end-to-end tests under src/vs/platform/agentHost/test/node/e2e (black-box tests that drive the whole agent host over the AHP protocol, using a CapiReplayProxy record/replay system for Claude/Copilot/Codex). Covers adding a cross-provider test…

microsoft/vscode · 104 tokens

fix-errors

Guidelines for fixing unhandled errors from the VS Code error telemetry dashboard. Use when investigating error-telemetry issues with stack traces, error messages, and hit/user counts. Covers tracing data flow through call stacks, identifying producers of invalid data vs. consumers that crash, enriching error messages…

microsoft/vscode · 75 tokens