agentleFS
zyphr-labszyphr-labs/bounty-harness/.claude/skills/cloud/SKILL.md

cloud

Skill1 starsChanged 3 months agoMITView on GitHub

This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start with s3-buckets unless prior evidence points to a more specific workflow.

    line 16
  2. Very specific:

    Follow each workflow next mapping in skill.yaml after reviewing generated findings.

    line 17
  3. Distinctive:

    If a workflow has no script reference, treat it as a manual or tool-native workflow and use the closest phase runbook when available.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cloud

Overview

Multi-cloud security testing — S3/GCP/Azure storage buckets, IAM enumeration, Lambda/Cloud Functions, metadata attacks, container registry, K8s clusters

This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.

Quick Reference

  • Skill: cloud
  • Severity range: medium, high, critical
  • Required tools: aws, gcloud, az, curl, ffuf, python3, dnsx, subfinder, jq, openssl, trufflehog
  • Expected input files: takeover_candidates.txt, all_urls.txt, live_urls.txt
  • Scope check: confirm authorization before running intrusive or authenticated testing.

Workflow Selection

  • Start with s3-buckets unless prior evidence points to a more specific workflow.
  • Follow each workflow next mapping in skill.yaml after reviewing generated findings.
  • If a workflow has no script reference, treat it as a manual or tool-native workflow and use the closest phase runbook when available.
  • Runbooks: use runbooks/ and select the closest phase runbook when workflow names do not map 1:1.

Available Workflows

WorkflowPurposeScript pathsPrimary outputsEvidence
s3-bucketsEnumerate likely S3 bucket names and test for public exposure..claude/skills/cloud/scripts/s3_bucket_enumerator.py$OUTDIR/cloud/aws/s3/findings.jsonl$OUTDIR/cloud/aws/s3/evidence/
aws-iam-privescScan the configured AWS profile for IAM privilege escalation paths..claude/skills/cloud/scripts/iam_privesc_scanner.py$OUTDIR/cloud/aws/iam/findings.jsonl$OUTDIR/cloud/aws/iam/evidence/

Evidence Required

  • Save raw request and response data for each confirmed finding.
  • Include timestamps, affected target, exact workflow name, tool versions, and reproduction steps.
  • Store screenshots or terminal captures in the workflow evidence directory when the workflow defines one.
  • Evidence templates from skill.yaml:
  • s3_public_object: curl response showing S3 object accessible without auth
  • iam_priv_esc: Policy document showing privilege escalation path
  • metadata_creds: Extracted AWS/GCP/Azure credentials from metadata service

References

  • Source of truth: skill.yaml
  • Runbooks: runbooks/
  • OWASP mappings: none listed in skill.yaml.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.