Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/richfrem/agent-plugins-skillsnpx agentmods add skills/richfrem/agent-plugins-skills/github-issue-worktree-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/richfrem/agent-plugins-skills/github-issue-worktree-agent)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/github-issue-worktree-agent"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/github-issue-worktree-agent/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/richfrem/agent-plugins-skills/github-issue-worktree-agent"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/github-issue-worktree-agent.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.00084 | $0.00703 |
| Opus 5.5 | $0.00034 | $0.00281 |
| Sonnet 5.5 | $0.00017 | $0.00141 |
| Haiku 4.5 | $0.00008 | $0.00070 |
Grade A, and why
github-issue-worktree-agent 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 17d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Worktree Agent (github-issue-worktree-agent)
Provisions and manages isolated git worktrees (.worktrees/issue-NNN) for clean issue execution branches.
Contents
Critical Constraints
- Scope Boundary: USE ONLY for worktree lifecycle operations. DO NOT USE for PR lifecycles (use
github-issue-pr-lifecycle-agent) or issue logging (usegithub-issue-agent). - Standard Location: Worktrees must strictly reside within
.worktrees/issue-NNNrelative to repository root. - Safe Teardown: Check
git statusprior to removal; never force-prune uncommitted work without confirmation. - Branch Tracking: Branch naming must consistently map to the issue identifier (
issue-NNN).
Quick start
# Provision isolated worktree for Issue #123
python3 plugins/dev-utils/skills/github-issue-worktree-agent/scripts/issue_worktree_manage.py \
create --issue 123 --base main
# List active worktrees
python3 plugins/dev-utils/skills/github-issue-worktree-agent/scripts/issue_worktree_manage.py list
# Clean up worktree after resolution
python3 plugins/dev-utils/skills/github-issue-worktree-agent/scripts/issue_worktree_manage.py \
remove --issue 123
Workflow
- Phase 1: Workspace Inspection: Check for existing worktree directories or branch name collisions.
- Phase 2: Worktree Provisioning: Spawn isolated worktree at
.worktrees/issue-NNNtracking trunk. - Phase 3: Implementation Context: Guide agent execution to occur within the isolated worktree directory.
- Phase 4: Teardown & Pruning: Confirm committed state, prune worktree directory, and clean local branch.
Verification
# Verify active worktree state
python3 plugins/dev-utils/skills/github-issue-worktree-agent/scripts/issue_worktree_manage.py list
# Audit skill compliance
python3 plugins/agent-scaffolders/scripts/audit_skill.py plugins/dev-utils/skills/github-issue-worktree-agent --mode source
What ships with it
6 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.
- 17d ago Changed · +23 lines 5622b9ecde4b
- 1mo ago First seen · 48 lines · 84 tokens per session scan A 3f33c0478ab0
github-issue-worktree-agent is a skill published in the GitHub repository richfrem/agent-plugins-skills (7 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 703 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-09-12.
Other skills, from other repositories
release
Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks for a stable version bump, tag, or GitHub Release. Never use for release candidates; NAC RC releases are automated.
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
factory-handoff
Hand one exact agent-ready ticket to the central Factory runtime over the configured SSH forced-command boundary. Use when an operator asks to hand off an existing ticket or a prose request instead of implementing it in the current session.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
release-revoke
Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish…
ap-work-group-manager
Divide one accepted work group only when at least two useful workers can have non-overlapping ownership.