lean-cloud
Skill2 starsChanged 55 days agoMITView on GitHub
Runs token-efficient defensive cloud and IAM reviews for Cursor and Codex. Inventories wildcard policies, public buckets, IMDS, and admin roles in local Terraform, Bicep, CDK, and cloud JSON, then reports compact hardening fixes. Use when the user asks for cloud security, IAM, S3/GCS buckets, security groups, IRSA, metadata service, or least privilege. Do not use for attacking cloud accounts, stealing keys, or scanning other tenants.
In this repository21 other files it gives its agents.
- lean-cryptoSkill
- lean-mobileSkill
- lean-privacySkill
- lean-secSkill
- lean-webSkill
- lean-a11ySkill
- lean-depsSkill
- lean-docsSkill
- lean-perfSkill
- lean-reviewSkill
- lean-ciSkill
- lean-costSkill
- lean-hardeningSkill
- lean-iotSkill
- lean-netSkill
- lean-dfirSkill
- lean-ir-playbookSkill
- lean-malwareSkill
- lean-osintSkill
- lean-phishSkill
- lean-threat-modelSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Distinctive: line 26
Do not call cloud APIs against accounts the user did not open in this workspace.
- Very specific: line 30
Default lean. deep only if asked.
- Very specific: line 40
Run iam. Queue wildcards, Principal "*", public ACLs, admin managed policies, IMDS v1, 0.0.0.0/0 on data stores.
- Distinctive: line 47
No exploit, privilege-escalation recipes, or key theft.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Lean Cloud
Defensive review of local cloud config. Scripts list risky IAM and storage lines; you confirm a few files; you patch only when asked.
Let SKILL_ROOT be the folder that contains this SKILL.md. Prefer python3; on Windows use py -3.
python3 "$SKILL_ROOT/scripts/lean_cloud.py" iam .
python3 "$SKILL_ROOT/scripts/lean_cloud.py" trim --chars 2500 path/to/out.txtDo not call cloud APIs against accounts the user did not open in this workspace. Do not dump full IAM JSON.
Mode
Default lean. deep only if asked.
| Mode | Budget |
lean | iam + up to 8 slices; references/iam.md; ≤6 findings |
standard | + references/storage.md; up to 16 slices; ≤10 findings |
deep | needed refs only; ≤16 findings |
Workflow
- Run
iam. Queue wildcards,Principal "*", public ACLs, admin managed policies, IMDS v1,0.0.0.0/0on data stores. - Slice-read the matching
.tf/ Bicep / SAM / K8s service-account annotations. - Report least-privilege fixes. Stop unless asked to patch.
Hard rules
- Workspace config only. No live
sts, no enumerating someone else's org. - No exploit, privilege-escalation recipes, or key theft.
- Cap quotes at 12 lines. Never print secret values.
Report template
## Lean-cloud (`<mode>`)
**Account/stack:** <name or folder> | **Budget:** files_read=<n>
| Sev | Location | Issue | Fix |
|-----|----------|-------|-----|
| HIGH | file:line | wildcard Action/Resource | split by service; constrain Resource |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
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.

