SaferSkills independently audited yeet (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
✓—All security checks passedNo findings in this category for the latest scan.pass
Supply chainscore 100 · 0 findings
✓—All supply chain checks passedNo findings in this category for the latest scan.pass
Maintenancescore 100 · 0 findings
✓—All maintenance checks passedNo findings in this category for the latest scan.pass
Transparencyscore 100 · 0 findings
✓—All transparency checks passedNo findings in this category for the latest scan.pass
Communityscore 100 · 0 findings
✓—All community checks passedNo findings in this category for the latest scan.pass
Every scanned point with the score it earned and what moved between them.
1 scans · 90 days
25ab877
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
bundled/skills/yeet/SKILL.md · 1 file
bundled/skills/yeet/SKILL.md1.7 KB · Markdown
name: "yeet"
description: "Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`)."
Prerequisites
Require GitHub CLI gh. Check gh --version. If missing, ask the user to install gh and stop.
Require authenticated gh session. Run gh auth status. If not authenticated, ask the user to run gh auth login (and re-run gh auth status) before continuing.
Naming conventions
Branch: codex/{description} when starting from main/master/default.
Commit: {description} (terse).
PR title: [codex] {description} summarizing the full diff.
Workflow
If on main/master/default, create a branch: git checkout -b "codex/{description}"
Otherwise stay on the current branch.
Confirm status, then stage everything: git status -sb then git add -A.
Commit tersely with the description: git commit -m "{description}"
Run checks if not already. If checks fail due to missing deps/tools, install dependencies and rerun once.
Push with tracking: git push -u origin $(git branch --show-current)
If git push fails due to workflow auth errors, pull from master and retry the push.
Open a PR and edit title/body to reflect the description and the deltas: GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --head $(git branch --show-current)
Write the PR description to a temp file with real newlines (e.g. pr-body.md ... EOF) and run pr-body.md to avoid \\n-escaped markdown.
PR description (markdown) must be detailed prose covering the issue, the cause and effect on users, the root cause, the fix, and any tests or checks used to validate.