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 TweekFawkes/prompts --skill gitreadygit clone --depth 1 https://github.com/TweekFawkes/promptsWrote 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/tweekfawkes/prompts/gitready)<a href="https://agentmods.dev/skills/tweekfawkes/prompts/gitready"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/gitready/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/tweekfawkes/prompts/gitready"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/gitready.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.00059 | $0.01550 |
| Opus 5.5 | $0.00024 | $0.00620 |
| Sonnet 5.5 | $0.00012 | $0.00310 |
| Haiku 4.5 | $0.00006 | $0.00155 |
Grade A, and why
gitready 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gitready - Prepare an isolated agent worktree
Use this skill to give each agent its own branch, worktree, dependency install, local runtime state, and handoff note. The default posture is: one task, one worktree, one branch, one agent.
Quick Start
- Read the repo root
CLAUDE.md(orAGENTS.md) and any localtasks/lessons.mdbefore creating the worktree. - Choose a short task slug: lowercase words separated by hyphens, such as
fix-rbac-export. - From anywhere inside the source repo, run:
repo_root="$(git rev-parse --show-toplevel)"
bash "$repo_root/.claude/skills/gitready/scripts/create_worktree.sh" <task-slug>
Useful options:
bash "$repo_root/.claude/skills/gitready/scripts/create_worktree.sh" <task-slug> --dry-run
bash "$repo_root/.claude/skills/gitready/scripts/create_worktree.sh" <task-slug> --base origin/main
bash "$repo_root/.claude/skills/gitready/scripts/create_worktree.sh" <task-slug> --branch agent/<task-slug>
bash "$repo_root/.claude/skills/gitready/scripts/create_worktree.sh" <task-slug> --path /absolute/worktree/path
bash "$repo_root/.claude/skills/gitready/scripts/create_worktree.sh" <task-slug> --no-fetch
The helper creates a timestamped agent/<task-slug>-<YYYYMMDDHHMMSS> branch by default and places the worktree in a sibling directory named <repo>-worktrees/<task-slug>-<timestamp>, outside the tracked repo. For a repo at /path/to/repo, worktrees land under /path/to/repo-worktrees/, and gitclean retires them under /path/to/repo-worktrees/delete_me/.
Generated branch/path collisions in the same second get a deterministic numeric suffix such as -2. A custom --path must be outside the tracked repository.
Seeding gitignored local state into the new worktree
A fresh worktree only contains tracked files — anything gitignored (env files, local secrets, seeded config) simply isn't there, even though the project may not run without it. If your project needs that, set it up once:
cp "$repo_root/.claude/skills/gitready/scripts/worktree-seed-paths.example" "$repo_root/.worktree-seed-paths"
# edit .worktree-seed-paths to list what your project actually needs, then commit it
What ships with it
3 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.
- 2mo ago First seen · 108 lines · 59 tokens per session scan A 3d5c2a1025a0
gitready is a skill published in the GitHub repository TweekFawkes/prompts (2 stars, last pushed 1mo ago), licensed Unlicense. It adds 59 tokens to every session and 1,550 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
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.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.