s3-estate-calibration-auditor

s3-estate-calibration-auditor is a skill for Claude Code from anyshift-io/sre-skills. It costs 293 tokens per session (5,474 once invoked), scanned A, original, Apache-2.0.

An audit skill for finding which Amazon S3 storage bucket is actually public or accessible by another account. It combines bucket settings, policies, access lists, and access points to determine the effective exposure.

In plain words
What is it for?
It reviews configuration files for multiple S3 buckets, ranks real exposures by severity, suggests a fix, and identifies where the available configuration cannot give a clear answer.
Why use it?
A single S3 setting can look dangerous while another setting prevents access, so checking each layer alone can create false alarms. It helps identify the genuinely exposed bucket across a group of buckets.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the sre-skills plugin — 5 skills shipped together

Good fit It reviews configuration files for multiple S3 buckets, ranks real exposures by severity, suggests a fix, and identifies where the available configuration cannot give a clear answer.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/anyshift-io/sre-skills/s3-estate-calibration-auditor
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.

Any agent
npx skills add anyshift-io/sre-skills --skill s3-estate-calibration-auditor
Clone the repo
git clone --depth 1 https://github.com/anyshift-io/sre-skills

Made for: Claude Code.

Or install sre-skills, the plugin that ships this one along with the rest of its 5 skills.

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

agentmods badge for s3-estate-calibration-auditor

README.md
[![agentmods](https://agentmods.dev/badge/skills/anyshift-io/sre-skills/s3-estate-calibration-auditor/github.svg)](https://agentmods.dev/skills/anyshift-io/sre-skills/s3-estate-calibration-auditor)
Your own site
<a href="https://agentmods.dev/skills/anyshift-io/sre-skills/s3-estate-calibration-auditor"><img src="https://agentmods.dev/badge/skills/anyshift-io/sre-skills/s3-estate-calibration-auditor/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for s3-estate-calibration-auditor

Your own site · 80×15
<a href="https://agentmods.dev/skills/anyshift-io/sre-skills/s3-estate-calibration-auditor"><img src="https://agentmods.dev/badge/skills/anyshift-io/sre-skills/s3-estate-calibration-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 293 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,474 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00293 $0.05474
Opus 5 $0.00147 $0.02737
Sonnet 5 $0.00059 $0.01095
Haiku 4.5 $0.00029 $0.00547

Measured 12d ago against content hash 0bb14327d060, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

s3-estate-calibration-auditor 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 12d 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.

skills/s3-estate-calibration-auditor/SKILL.md · 348 lines

How it starts

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

s3-estate-calibration-auditor

Effective-exposure audit skill for an estate of AWS S3 buckets. Takes the config layers for every bucket in the estate (public-access-block.json, bucket-policy.json, bucket-acl.json, and access-points.json where present), resolves each bucket's effective verdict by composing all four layers, then answers one question a per-layer read cannot: across 8-12 buckets that mostly READ as exposed, which one is genuinely live, and is the estate otherwise clean. It returns the live bucket as the headline, ranked by severity, with a fix, then names exactly where the bucket configs stop being able to answer the question.

Effective S3 exposure is a join across four layers that each get read wrong one at a time. A public-looking bucket policy is inert under RestrictPublicBuckets; a cross-account grant survives BPA-all-on; a public-group ACL is dead under IgnorePublicAcls but a cross-account canonical user beside it is not; a clean bucket can still be public through an access point. In an estate, the trap doubles: several buckets carry a Principal '*' policy, an AllUsers ACL, or a wide-open look that is genuinely neutralised, and exactly one bucket carries a real live grant that reads just like its neutralised siblings. This skill composes the layers per bucket instead of clearing each layer in isolation, then calibrates the estate: it does not over-flag the neutralised baits, and it does not miss the buried needle.

When to invoke

  • An agent is asked to review an S3 bucket fleet for public exposure, cross-account access, or "is anything in this account public."
  • An estate is being shipped or changed and the question is whether any bucket is effectively exposed, not just whether a Principal '*' or an AllUsers grant appears somewhere in the configs.
  • An estate looks exposed (several Principal '*' policies, AllUsers ACLs) and the claim "but BPA is on / it is scoped" needs to be confirmed against the effective verdict rather than taken on trust.
  • An estate looks locked down (BPA all on everywhere) and the claim "the account is closed" needs to be checked against the cross-account grants BPA does not touch.

Read the full file on GitHub · 348 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 12d ago First seen · 348 lines · 0 tokens per session scan A 0bb14327d060

Subscribe to this mod's changes

s3-estate-calibration-auditor is a skill published in the GitHub repository anyshift-io/sre-skills (17 stars, last pushed 15d ago), licensed Apache-2.0. It adds 293 tokens to every session and 5,474 once invoked, about $0.0015 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-30.