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 jesse-merhi/skills --skill just-do-itgit clone --depth 1 https://github.com/jesse-merhi/skillsWrote 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/jesse-merhi/skills/just-do-it)<a href="https://agentmods.dev/skills/jesse-merhi/skills/just-do-it"><img src="https://agentmods.dev/badge/skills/jesse-merhi/skills/just-do-it/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.
<a href="https://agentmods.dev/skills/jesse-merhi/skills/just-do-it"><img src="https://agentmods.dev/badge/skills/jesse-merhi/skills/just-do-it.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.01697 |
| Opus 5.5 | $0.00018 | $0.00679 |
| Sonnet 5.5 | $0.00009 | $0.00339 |
| Haiku 4.5 | $0.00004 | $0.00170 |
Grade A, and why
just-do-it 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Just Do It
Take a small, well-defined change from whatever verified checkpoint it has reached to a non-draft PR that is ready for Jesse to inspect. Continue correct existing work instead of restarting it. Keep moving through ordinary implementation and delivery decisions without asking for intermediate approval.
Invoking this skill grants bounded authority to create a feature branch, make
local commits, make normal pushes to that branch, create or update one PR, edit
its title and body, upload required proof, change its draft/ready state, and run the full
code-review workflow. It does not authorize force-push, merge, deployment,
manual labels, PR reactions, prose comments, destructive operations, new
dependencies, breaking changes, or work outside the requested change.
Fit check
Use this workflow only when the requested outcome and acceptance behavior are already clear and the work belongs in one cohesive PR. Stop and ask before continuing when a missing product decision, breaking change, new dependency, security disclosure, production mutation, or multi-PR delivery shape would materially change the assignment. Do not squeeze larger work into this workflow merely because the skill was invoked.
Repository instructions remain authoritative. Apply their project-specific validation and delivery gates without copying those rules into this generic skill. A repository gate may make the PR harder to finish, but it does not expand the requested implementation scope.
Resume rule
Treat this workflow as a resumable checkpoint chain, not a mandatory restart. Inspect the local and remote evidence before acting: worktree, branch, base, net diff, commits, PR metadata and authorship, remote head, review closeout, proof, required checks, and repository-specific gates. Classify each workflow step as current, incomplete, stale, or not applicable. A chat claim, task status, or old passing result is not evidence unless it still matches the current tree or exact remote head.
What ships with it
1 file 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.
- 2mo ago First seen · 154 lines · 44 tokens per session scan A a714b4ea2dc1
just-do-it is a skill published in the GitHub repository jesse-merhi/skills (4 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 1,697 once invoked, about $0.0002 per session on Opus 5.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
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…