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 GabsFranke/claude-code-github-agent --skill git-worktree-workflowgit clone --depth 1 https://github.com/GabsFranke/claude-code-github-agentWrote 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/gabsfranke/claude-code-github-agent/git-worktree-workflow)<a href="https://agentmods.dev/skills/gabsfranke/claude-code-github-agent/git-worktree-workflow"><img src="https://agentmods.dev/badge/skills/gabsfranke/claude-code-github-agent/git-worktree-workflow/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/gabsfranke/claude-code-github-agent/git-worktree-workflow"><img src="https://agentmods.dev/badge/skills/gabsfranke/claude-code-github-agent/git-worktree-workflow.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.00082 | $0.02192 |
| Opus 5.5 | $0.00033 | $0.00877 |
| Sonnet 5.5 | $0.00016 | $0.00438 |
| Haiku 4.5 | $0.00008 | $0.00219 |
Grade A, and why
git-worktree-workflow 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 1mo 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Worktree Workflow Skill
This skill provides essential knowledge for agents working in isolated git worktrees. Use this to understand your workspace and how to work with files and git.
Your Workspace Environment
CRITICAL: You Are Already in a Git Worktree
DO NOT clone the repository! You are already working in an isolated git worktree.
- Your current directory IS the repository
- All files are already available locally
- Git credentials are pre-configured
- The repository is ready for you to work
What is a Git Worktree?
A worktree is an isolated working directory linked to a shared git repository. Multiple worktrees can exist simultaneously without interfering with each other.
Key characteristics:
- Isolated file system (your changes don't affect other jobs)
- Shared git history (commits are visible across worktrees)
- Pre-configured credentials (git push works automatically)
Check Your Current State
# Check if you're on a branch or in detached HEAD
git status
# If on a branch, see which one
git branch --show-current
# See recent commits
git log -1 --oneline
File Operations
Reading and Analyzing Files
Use these tools to explore the codebase:
- Read - Read file contents
- List - List directory contents
- Search - Search for files by name
- Grep - Search for text patterns in files
- Bash - Run shell commands for complex operations
# Find all Python test files
find tests/ -name "test_*.py"
# Search for specific error patterns
grep -r "import requests" src/
# Check current directory
pwd
ls -la
Modifying Files
Use these tools to implement fixes:
- Write - Create new files or overwrite existing ones
- Edit - Make targeted changes to existing files
- Bash - Run commands that modify files (formatters, etc.)
# Run auto-formatters (use virtual environment)
.venv/bin/black src/
.venv/bin/isort src/
.venv/bin/ruff check --fix .
# Run tests locally (use virtual environment)
.venv/bin/python -m pytest tests/
npm test
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.
- 1mo ago First seen · 353 lines · 82 tokens per session scan A ea4caf42333b
git-worktree-workflow is a skill published in the GitHub repository GabsFranke/claude-code-github-agent (5 stars, last pushed 26d ago), licensed MIT. It adds 82 tokens to every session and 2,192 once invoked, about $0.0003 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.