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/richfrem/agent-plugins-skills/issue-worktree-agentnpx skills add richfrem/agent-plugins-skills --skill issue-worktree-agentgit clone --depth 1 https://github.com/richfrem/agent-plugins-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/richfrem/agent-plugins-skills/issue-worktree-agent)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/issue-worktree-agent"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/issue-worktree-agent.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.00075 | $0.00614 |
| Opus 5 | $0.00037 | $0.00307 |
| Sonnet 5 | $0.00015 | $0.00123 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
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 yesterday.
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.
Issue Worktree Agent (issue-worktree-agent)
Routing Directive: USE ONLY when setting up, listing, or removing isolated git worktrees (
.worktrees/issue-NNN) for issue execution branches. DO NOT USE for managing local scratch tasks (usetask-agentinstead) or managing GitHub PR lifecycles (useissue-pr-lifecycle-agentinstead).
The issue-worktree-agent skill manages isolated workspace environments using git worktree. It ensures agent work on specific issues takes place in isolated branches under .worktrees/issue-NNN without dirtying or interfering with the main working directory.
Safety & Security Contracts
- Path Isolation: All worktrees created by this skill are strictly scoped within
.worktrees/issue-NNN. - Branch Management: Automatically creates feature branches named
issue-NNN(or a custom branch name) off a specified base branch (default:main). - Safe Cleanup: Worktree removal requires explicit call; supports
--forceflag for uncommitted change cleanup.
Usage catalog
Create, List, and Remove Worktrees
- Helper Script:
plugins/dev-utils/skills/issue-worktree-agent/scripts/issue_worktree_manage.py - CLI Usage:
# Create a worktree for Issue #123: python3 plugins/dev-utils/skills/issue-worktree-agent/scripts/issue_worktree_manage.py create --issue 123 --base main # List active worktrees: python3 plugins/dev-utils/skills/issue-worktree-agent/scripts/issue_worktree_manage.py list # Remove a worktree for Issue #123: python3 plugins/dev-utils/skills/issue-worktree-agent/scripts/issue_worktree_manage.py remove --issue 123
Python API Interface
from plugins.dev_utils.skills.issue_worktree_agent.scripts.issue_worktree_manage import (
create_worktree,
list_worktrees,
remove_worktree,
)
# Create worktree
res = create_worktree(issue_number=123, branch_name="fix-issue-123", base_branch="main")
# List worktrees
worktrees = list_worktrees()
# Remove worktree
remove_worktree(issue_number=123, force=False)
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.
- yesterday First seen · 71 lines · 75 tokens per session scan A 2a59e116e3a4
issue-worktree-agent is a skill published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 614 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
kapso-whatsapp
How to interact with Kapso WhatsApp from the swarm — read inbound webhook payloads (text AND media), fetch message history, send free-form messages within the 24h session window (and template messages outside it), mark-as-read, show the typing indicator, send reactions, download media, verify webhook signatures, and…
composio
Use Composio from Agent Swarm through the agent-swarm x composio CLI route, the swarmx MCP tool, or a registered ctx.api.composio script connection. Trigger when a task needs connected third-party app tools such as Gmail, Google Calendar, Google Docs, Google Drive, GitHub, Slack, Notion, or HubSpot through Tool Router…
attio-interaction
Generic Attio CRM REST API v2 recipes for querying records, upserting companies/people/deals, writing notes/tasks/comments, managing lists, and handling webhooks.
swarm-scripts
Bulk, repeat, fan-out, or data-heavy work: write and run swarm scripts (inline script-run, named script-upsert, durable launch-script-run). Covers the script-vs-tool rubric, the authoring contract (args first, ctx second), the seed catalog, connections and secrets, dbquery, and exposing a script as an API.
user-management
How to manage the user registry — creating users for new Slack/GitHub/GitLab/Linear identities, managing aliases, resolving users across platforms. Use when a new human interacts with the swarm or when user identity needs updating.
scheduled-task-resilience
Guardrails for polling, scheduled jobs, and long-running external operations. Use whenever a task waits on CI, builds, deploys, browser jobs, or another asynchronous API so work survives heartbeat checks without duplicate delivery.