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.
npx skills add rojim666/SztuCode --skill yeetgit clone --depth 1 https://github.com/rojim666/SztuCodeWrote 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.
[](https://agentmods.dev/skills/rojim666/sztucode/yeet)<a href="https://agentmods.dev/skills/rojim666/sztucode/yeet"><img src="https://agentmods.dev/badge/skills/rojim666/sztucode/yeet.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00049 | $0.00903 |
| Opus 5 | $0.00024 | $0.00451 |
| Sonnet 5 | $0.00010 | $0.00181 |
| Haiku 4.5 | $0.00005 | $0.00090 |
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.
This is a copy
100% identical to yeet — 140 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Publish Changes
Overview
Use this skill only when the user explicitly wants the full publish flow from the local checkout: branch setup if needed, staging, commit, push, and opening a pull request.
This workflow is hybrid:
- Use local
gitfor branch creation, staging, commit, and push. - Prefer the GitHub app from this plugin for pull request creation after the branch is on the remote.
- Use
ghas a fallback for current-branch PR discovery, auth checks, or PR creation when the connector path cannot infer the repository or head branch cleanly.
Prerequisites
- Require GitHub CLI
gh. Checkgh --version. If missing, ask the user to installghand stop. - Require authenticated
ghsession. Rungh auth status. If not authenticated, ask the user to rungh auth login(and re-rungh auth status) before continuing. - Require a local git repository with a clean understanding of which changes belong in the PR.
Naming conventions
- Branch:
codex/{description}when starting from main/master/default. - Commit:
{description}(terse). - PR title:
[codex] {description}summarizing the full diff.
Workflow
- Confirm intended scope.
- Run
git status -sband inspect the diff before staging. - If the working tree contains unrelated changes, do not default to
git add -A. Ask the user which files belong in the PR.
- Run
- Determine the branch strategy.
- If on
main,master, or another default branch, createcodex/{description}. - Otherwise stay on the current branch.
- If on
- Stage only the intended changes.
- Prefer explicit file paths when the worktree is mixed.
- Use
git add -Aonly when the user has confirmed the whole worktree belongs in scope.
- Commit tersely with the confirmed description.
- Run the most relevant checks available if they have not already been run.
- If checks fail due to missing dependencies or tools, install what is needed and rerun once.
- Push with tracking:
git push -u origin $(git branch --show-current). - Open a draft PR.
- Prefer the GitHub app from this plugin for PR creation after the push succeeds.
- Derive
repository_full_namefrom the remote, for example by normalizinggit remote get-url originor by usinggh repo view --json nameWithOwner. - Derive
head_branchfromgit branch --show-current. - Derive
base_branchfrom the user request when specified; otherwise use the remote default branch, for example viagh repo view --json defaultBranchRef. - If the branch is being pushed from a fork or the PR target differs from the remote that was just pushed, prefer
gh pr createfallback because the connector PR creation flow expects one repository target and may not encode cross-repo head semantics cleanly. - If connector-based PR creation cannot infer the repository or branch cleanly, fall back to
gh pr create --draft --fill --head $(git branch --show-current). - Write the PR body to a temp file with real newlines when using CLI fallback so the markdown renders cleanly.
- Summarize the result with branch name, commit, PR target, validation, and anything the user still needs to confirm.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 71 lines · 49 tokens per session scan A 9d70c68282ac
yeet is a skill published in the GitHub repository rojim666/SztuCode (54 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 903 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to yeet, differing in 140 lines, and is treated as a copy.
Other skills, from other repositories
cross-repo-cache
Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSSREPOCACHEHIT with cached status or…
commit
A commit candidate is the exact patch that will enter the commit. A coherent change has one task or issue as its reason for existing.
commit
Inspect git status, draft a commit message that matches the repo's style, and commit staged changes.
promote
A workflow for sharing useful work from a separate Git worktree, which is another working folder linked to the same Git project, into the shared main branch.
coding-git-workflow
Use this skill to structure commits, branches, and pull/merge-request submission for a piece of work — commit granularity, branch lifetime, and what a PR description must state. It favors small reviewable slices over one large branch and treats a version number as a promise to consumers; do not use it for the code…
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.