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/arjunprabhulal/devops-skills/cdnnpx skills add arjunprabhulal/devops-skills --skill cdngit clone --depth 1 https://github.com/arjunprabhulal/devops-skillsWrote 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/arjunprabhulal/devops-skills/cdn)<a href="https://agentmods.dev/skills/arjunprabhulal/devops-skills/cdn"><img src="https://agentmods.dev/badge/skills/arjunprabhulal/devops-skills/cdn.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.1 | $0.00115 | $0.01275 |
| Opus 5 | $0.00057 | $0.00638 |
| Sonnet 5 | $0.00023 | $0.00255 |
| Haiku 4.5 | $0.00012 | $0.00128 |
Grade A, and why
cdn 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 5d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CDN
A CDN's entire value is serving a response without asking the origin, from a location physically closer to the user. Every problem in CDN configuration traces back to one question asked carelessly: is this response actually the same for the next request, or did it just look that way in testing? Get that wrong and you either serve one user's private data to another, or fail to cache anything and pay full origin cost with extra hops on top.
A cached response is a promise that this exact bytes-for-bytes answer is correct for anyone who asks the same question — verify that promise before you make it.
1. Define the cache key as precisely as the response varies
The cache key — usually URL plus a chosen set of headers/cookies/query params — determines what
counts as "the same request." Too narrow a key (ignoring a header the response actually varies by,
like Accept-Language or an auth cookie) causes one user's personalized or region-specific
response to be served to everyone else. Too broad a key (including a header that doesn't affect
the response, like a random request ID) destroys the cache hit rate by fragmenting it into
singletons.
- Include every header or param the response body actually varies on — check server-side
Varybehavior, don't assume. - Exclude anything that's unique per request but doesn't change the response — tracking IDs, timestamps in query strings, cache-busting params added out of habit.
- A cache key that's too narrow is a security bug, not just a correctness bug, if it leaks personalized content across users.
Done when: two requests that produce the same key always produce the same correct response for either requester.
2. Set TTL by how wrong a stale answer is allowed to be
Static assets with content-hashed filenames can cache essentially forever, because a new version gets a new URL — the old cached copy is never wrong, just superseded. Anything without that property needs a TTL chosen by asking how long a stale answer is tolerable: a product price is not the same tolerance as a blog post body.
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.
- 5d ago First seen · 102 lines · 115 tokens per session scan A 874f28589966
cdn is a skill published in the GitHub repository arjunprabhulal/devops-skills (3 stars, last pushed 11d ago), licensed MIT. It adds 115 tokens to every session and 1,275 once invoked, about $0.0006 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
google-cloud-solution-guided-gke-ai-migration
Guides the migration of existing AI workloads (Cloud Run, Gemini API, Gemini Enterprise Agent Platform) to self-hosted GKE inference using gcloud and kubectl. Use when the user has an existing AI inference workload (on Cloud Run, the Gemini API, Gemini Enterprise Agent Platform, or a custom VM) and wants to move it to…
agent-platform-deploy
Deploy open models or custom weights from Model Garden to Agent Platform endpoints, check the status of an in-progress deployment operation, or clean up resources by undeploying models and deleting endpoints. Use when asked to actively deploy a model, list the Model Garden CATALOG of available models, check if a…
cloud-logging-cross-project-configuration
Configure and troubleshoot Google Cloud cross-project centralized logging and read-time aggregation. Use when: - Setting up log routing from multiple projects/folders/organizations to a central log bucket. - Creating cross-project log sinks and configuring central log buckets. - Troubleshooting cross-project routing.…
gke-alert-configuration
Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using…
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
google-cloud-recipe-foundation-builder
Deploys a baseline landing zone foundation for a Google Cloud Organization, establishing security guardrails using Organization Policies, resource hierarchy folders and projects, billing association, and centralized logging and monitoring. Deploys Google Cloud's recommended security controls and architecture. Use when…