lean-ci
Skill2 starsChanged 57 days agoMITView on GitHub
Runs token-efficient defensive CI and supply-chain reviews for Cursor and Codex. Inventories GitHub Actions and GitLab CI for write-all permissions, unpinned actions, pull_request_target, and secret echoes, then reports compact pipeline hardening. Use when the user asks for CI security, GitHub Actions review, supply chain, unpinned actions, or workflow permissions. Do not use for exploiting CI, stealing secrets from other repos, or poisoning registries.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- instructa/agent-skillstheir own version, first seen Aug 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- instructa/agent-skills★ 139same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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-cloudSkill
- 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
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Do not dump npm audit JSON or lockfiles.
- Very specific: line 41
Run workflows. Queue write-all, pull_request_target, unpinned uses:, echo of secrets, checkout of untrusted PRs with secrets.
- Very specific: line 48
No payload in run: blocks.
≈ “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 CI
Defensive pipeline review of workflow files in this workspace. Scripts list risky jobs; 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_ci.py" workflows .
python3 "$SKILL_ROOT/scripts/lean_ci.py" trim --chars 2500 path/to/out.txtDo not dump npm audit JSON or lockfiles. Do not attack GitHub/GitLab.
Mode
Default lean.
| Mode | Budget |
lean | workflows + up to 8 slices; references/actions.md; ≤6 findings |
standard | + references/pins.md; up to 16 slices; ≤10 findings |
deep | needed refs only; ≤16 findings |
Workflow
- Run
workflows. Queuewrite-all,pull_request_target, unpinneduses:,echoof secrets, checkout of untrusted PRs with secrets. - Slice-read the workflow YAML.
- Report least privilege, pin-to-SHA, and fork isolation. Stop unless asked to patch.
Hard rules
- This repo's pipelines only. No abusing
pull_request_targetas an attack demo. - No payload in
run:blocks. Describe the unsafe pattern and the safer YAML. - Cap quotes at 12 lines.
Report template
## Lean-ci (`<mode>`)
**System:** GitHub Actions / GitLab CI | **Budget:** files_read=<n>
| Sev | Location | Issue | Fix |
|-----|----------|-------|-----|
| HIGH | file:line | pull_request_target + secrets | split jobs; do not share secrets with fork PRs |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.