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 skills add Goodsmileduck/claude-registry --skill cloud-storage-identificationgit clone --depth 1 https://github.com/Goodsmileduck/claude-registryWrote 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/goodsmileduck/claude-registry/cloud-storage-identification)<a href="https://agentmods.dev/skills/goodsmileduck/claude-registry/cloud-storage-identification"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/cloud-storage-identification.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.00080 | $0.01714 |
| Opus 5 | $0.00040 | $0.00857 |
| Sonnet 5 | $0.00016 | $0.00343 |
| Haiku 4.5 | $0.00008 | $0.00171 |
Grade C, and why
cloud-storage-identification scanned grade C 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 8d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
If endpoint is `None` / unset in code using boto3, the SDK defaults to AWS — confirm by looking at credentials (`AWS_PROFILE`, `~/.aws/credentials`). How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Object Storage — provider identification
Prevents the AWS-default trap: assuming any aws_s3_bucket resource or boto3 call is hitting AWS S3 when it's actually GCS, DO Spaces, Hetzner, R2, B2, MinIO, or Azure Blob.
When to invoke
Symptoms:
- A script uses
boto3or the AWS SDK but you don't seeimport boto3paired with explicit AWS credentials. - A Terraform module references an
aws_s3_bucketbut the backend or provider block points elsewhere. - A
rcloneconfig hasprovider = Otheror a custom endpoint. - The user says "the bucket" or "S3" without context.
- An error message mentions an endpoint that doesn't end in
amazonaws.com.
Failure mode this prevents: assuming AWS S3 and recommending AWS-specific tooling (IAM policies, S3 Lifecycle rules, CloudWatch metrics, presigned URL signing v4 quirks) when the actual target is a different provider with different auth, different features, and different bugs.
Step 1 — Identify the endpoint
Endpoint URL is the most reliable identifier. Look in: endpoint_url= kwarg, AWS_ENDPOINT_URL env, Terraform endpoints block, rclone config, s3cmd config, or the explicit URL in error messages.
| Endpoint pattern | Provider | Notes |
|---|---|---|
s3.<region>.amazonaws.com / <bucket>.s3.<region>.amazonaws.com |
AWS S3 | Real deal. Region required in v4 signing. |
s3-accelerate.amazonaws.com |
AWS S3 Transfer Acceleration | Different perf profile, same API. |
storage.googleapis.com |
Google Cloud Storage | XML API is S3-ish but not full compat; native JSON API is preferred. |
<region>.digitaloceanspaces.com |
DigitalOcean Spaces | S3-compat. Missing some headers (e.g. x-amz-tagging partial). |
<endpoint>.your-objectstorage.com (e.g. nbg1.your-objectstorage.com) |
Hetzner Object Storage | Path-style only; virtual-hosted style not supported. |
<account>.r2.cloudflarestorage.com |
Cloudflare R2 | No egress fees, requires auto as region. |
s3.<region>.backblazeb2.com |
Backblaze B2 (S3-compat API) | Native B2 API also exists and is different. |
<account>.blob.core.windows.net |
Azure Blob | Not S3-compat — different SDK entirely. |
<minio-host>:9000 or self-hosted IP/hostname |
MinIO or other self-hosted | Behavior varies by version. |
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.
- 8d ago First seen · 127 lines · 80 tokens per session scan C 3b4696f4206e
cloud-storage-identification is a skill published in the GitHub repository Goodsmileduck/claude-registry (1 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 1,714 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
devops-best-practices
Opinionated production-grade DevOps defaults for Terraform, Kubernetes, CI/CD, Docker, cloud security, observability, cost, and disaster recovery. ALWAYS use when generating, reviewing, or modifying any infrastructure code, Kubernetes manifests (Deployment, Service, StatefulSet, Helm, Kustomize), Terraform (.tf…
cloudflare-temporary-deploy
Deploy a Worker live, no account, via wrangler --temporary.
tensorrt-llm
High-throughput LLM inference on NVIDIA GPUs.
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.
cli-backup-sync
Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.