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/fisker086/aiops/s3_toolnpx skills add fisker086/AIOps --skill s3_toolgit clone --depth 1 https://github.com/fisker086/AIOpsWrote 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/fisker086/aiops/s3_tool)<a href="https://agentmods.dev/skills/fisker086/aiops/s3_tool"><img src="https://agentmods.dev/badge/skills/fisker086/aiops/s3_tool.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.00000 | $0.00698 |
| Opus 5 | $0.00000 | $0.00349 |
| Sonnet 5 | $0.00000 | $0.00140 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade C, and why
s3-tool 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 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.
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.
**Credentials:** Omit `access_key` and `secret_key` to use the default AWS chain (environment variables, `~/.aws/credentials` / `AWS_PROFILE`, or IAM role on the host). If no credentials are available, the tool returns a What it actually says
S3 Tool Skill
Credentials: Omit access_key and secret_key to use the default AWS chain (environment variables, ~/.aws/credentials / AWS_PROFILE, or IAM role on the host). If no credentials are available, the tool returns a short setup message instead of a raw SDK error—relay that to the user and do not ask them to paste secrets in chat.
Provides AWS S3 operations for storage management:
- list_buckets: List all S3 buckets
- list_objects: List objects in a bucket (with prefix filter)
- get_object: Get object content and metadata
- put_object: Upload object to bucket
- delete_object: Delete object from bucket
- head_object: Get object metadata without content
- get_presigned_url: Generate presigned URL for temporary access
Use builtin_s3_tool tool with fields:
operation: Operation name (list_buckets, list_objects, get_object, put_object, delete_object, head_object, get_presigned_url)region: AWS region for the S3 client; must match the bucket's region (defaultus-east-1only if the bucket is in us-east-1). Mismatch yieldsIllegalLocationConstraintException—use e.g.ap-east-1for Hong Kong buckets.access_key: (optional) AWS access key IDsecret_key: (optional) AWS secret access keysession_token: (optional) AWS session token for temporary credentialsbucket: S3 bucket namekey: Object key/pathcontent: Content to upload for put_objectcontent_base64: Base64 encoded content for put_objectcontent_type: Content-Type for put_object (e.g., application/json)prefix: Prefix filter for list_objectsmax_keys: Max objects to list (default: 100)download: Return full content for get_object (true/1)expires: Presigned URL expiry in seconds (default: 3600)
Example - list buckets:
operation: "list_buckets"
region: "us-east-1"
access_key: "AKIAIOSFODNN7EXAMPLE"
secret_key: "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
Example - list objects:
operation: "list_objects"
bucket: "my-bucket"
prefix: "logs/"
max_keys: "50"
Example - put object:
operation: "put_object"
bucket: "my-bucket"
key: "data/file.json"
content: '{"key": "value"}'
content_type: "application/json"
Example - get presigned URL:
operation: "get_presigned_url"
bucket: "my-bucket"
key: "private/data.csv"
expires: "3600"
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 · 68 lines · 0 tokens per session scan C 52d6bad6700a
s3-tool is a skill published in the GitHub repository fisker086/AIOps (22 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 698 tokens. 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…