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 agentmods add skills/jhostalek/dotclaude/yeetnpx skills add JHostalek/dotclaude --skill yeetgit clone --depth 1 https://github.com/JHostalek/dotclaudeWrote 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/jhostalek/dotclaude/yeet)<a href="https://agentmods.dev/skills/jhostalek/dotclaude/yeet"><img src="https://agentmods.dev/badge/skills/jhostalek/dotclaude/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 | $0.00038 | $0.00463 |
| Opus 5 | $0.00019 | $0.00231 |
| Sonnet 5 | $0.00008 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00046 |
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 5d 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.
What it actually says
input = $ARGUMENTS
Set audit_requested only when input contains the standalone phrase with audit, case-insensitively. Remove that phrase from input; the remainder is work. If no work remains, stop and ask for it.
Complete this workflow in order:
- Before any remote, Git, or file mutation, run resolve-skill.mjs once from the task's working directory. Resolve
mattpocock-skills:implement mattpocock-skills:tdd mattpocock-skills:code-review mattpocock-skills:setup-matt-pocock-skills jhostalek-skills:pr; appendjhostalek-skills:auditonly whenaudit_requested. Command:node <resolved-script-path> --cwd <task-cwd> <skills...>. Read every returnedpathcompletely and follow those instructions when invoked below. Treat unqualified skill references in a loaded plugin skill as belonging to that plugin's namespace. Stop before making changes if any requested dependency is missing, disabled, ambiguous, or unreadable. - Work only in the current checkout. Never create, select, switch, sync, or remove worktrees or branches.
- Use
mattpocock-skills:implementfor the requested work. - Use
jhostalek-skills:prto create or update the PR. - When
audit_requested, usejhostalek-skills:auditfor a full audit, pragmatically fix every valid finding within scope, then usejhostalek-skills:pragain to push the fixes and update the PR. Otherwise skip this step. - Merge the PR with the repository host's CLI and delete its remote source branch. Do not change the local checkout after merging.
Stop if a required skill, PR, check, or approval blocks the next step. Never bypass branch protection or failing required checks.
Report the merged PR and remote merge commit.
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.
- 5d ago First seen · 22 lines · 38 tokens per session scan A aa1d063a5f09
yeet is a skill published in the GitHub repository JHostalek/dotclaude (11 stars, last pushed today), licensed CC0-1.0. It adds 38 tokens to every session and 463 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-08-31.
Other skills, from other repositories
auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog.
hook-template
Generate hook script from template. Use when adding a new hook, wiring a PreToolUse/PostToolUse/Stop/Notification hook, or scaffolding hook config for settings.json.
skill-check
Validate skill/command file format and structure. Use after creating or editing a skill, before committing skill changes, or when a skill fails to load or trigger.
agent-check
Validate custom agent file format and structure. Use after creating or editing an agent, before committing agent changes, or when an agent fails to load.
skill-template
Generate custom skill/command from template. Use when creating a new skill or slash command from scratch, or scaffolding a skill file with correct frontmatter.
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.