yeet

yeet is a skill for Claude Code, Codex from Kevin-Liu-01/Agent-Machines. It costs 35 tokens per session (418 once invoked), scanned A, original, MIT.

A GitHub workflow for staging changes, creating a commit, pushing a branch, and opening a pull request with the GitHub CLI. It is intended for cases where the user explicitly requests the complete flow.

In plain words
What is it for?
Use it to send a completed code change from the local Git repository to a GitHub pull request.
Why use it?
It removes the need to perform the same branch, authentication, commit, push, and pull-request checks manually.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex.

Good fit Use it to send a completed code change from the local Git repository to a GitHub pull request.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kevin-liu-01/agent-machines/yeet
Install

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.

Any agent
npx skills add Kevin-Liu-01/Agent-Machines --skill yeet
Clone the repo
git clone --depth 1 https://github.com/Kevin-Liu-01/Agent-Machines

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for yeet

README.md
[![agentmods](https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/yeet/github.svg)](https://agentmods.dev/skills/kevin-liu-01/agent-machines/yeet)
Your own site
<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/yeet"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/yeet/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for yeet

Your own site · 80×15
<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/yeet"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/yeet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 418 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.00418
Opus 5 $0.00017 $0.00209
Sonnet 5 $0.00007 $0.00084
Haiku 4.5 $0.00003 $0.00042

Measured 8d ago against content hash 2b4583b296a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

yeet scanned grade A with 0 findings 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 8d 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • yeet — 91% identical, 6 lines differ
knowledge/skills/yeet/SKILL.md · 29 lines

What it actually says

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.
Changes

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.

  1. 8d ago First seen · 29 lines · 35 tokens per session scan A 2b4583b296a3

Subscribe to this mod's changes

yeet is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (29 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 418 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…

cyanheads/obsidian-mcp-server · 104 tokens

studio-source-control

Drive a scoped application's linked git repository from the instance — what has to be true before Source Control works at all, the commit-then-push order, stashes and branches over /api/snsourcecontrol, and when this replaces update sets rather than sitting next to them.

serac-labs/serac · 59 tokens

git-wrapup

Review verified mcp-reporter changes, prepare versioned changelog entries, create logical commits and an annotated local tag. No push or publish.

cyanheads/mcp-reporter · 33 tokens

git-conventional-commits

Author standardized conventional commit messages (feat, fix, docs, refactor, chore), generate automated semver releases, and format pull request descriptions.

pedroiff0/awesome-skills · 36 tokens

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…

cyanheads/pubmed-mcp-server · 104 tokens

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…

cyanheads/mcp-ts-core · 104 tokens