Borrowing it
Nothing to install: this file belongs to tatargabor/set-core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tatargabor/set-core/main/.claude/skills/set/SKILL.mdgit clone --depth 1 https://github.com/tatargabor/set-coreWrote 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/tatargabor/set-core/set)<a href="https://agentmods.dev/skills/tatargabor/set-core/set"><img src="https://agentmods.dev/badge/skills/tatargabor/set-core/set.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.1 | $0.00038 | $0.01435 |
| Opus 5 | $0.00019 | $0.00718 |
| Sonnet 5 | $0.00008 | $0.00287 |
| Haiku 4.5 | $0.00004 | $0.00144 |
Grade A, and why
set 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 today.
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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Management Skill
Manage git worktrees for parallel AI agent development.
Context Detection
First, detect which mode you're operating in:
# Check if we're in a worktree (not the main repo)
if git rev-parse --is-inside-work-tree &>/dev/null; then
BRANCH=$(git branch --show-current)
if [[ "$BRANCH" == change/* ]]; then
CHANGE_ID="${BRANCH#change/}"
echo "Running in worktree: $CHANGE_ID"
MODE="worktree"
else
echo "Running in main repository"
MODE="main"
fi
fi
Central Control Commands
Use these from the main repository to manage worktrees.
List Worktrees
set-list
List all active worktrees with their change IDs and paths.
To see remote branches available for checkout:
set-list --remote
Create New Worktree
set-new <change-id>
Creates a new worktree at ../<project>-<change-id>/ with branch change/<change-id>.
If the branch exists on remote, it will be checked out and tracked automatically.
To force create a new branch even if remote exists:
set-new <change-id> --new
Open Worktree for Work
set-work <change-id>
Opens the worktree in Zed editor with Claude Code. This launches a new agent session in that worktree context.
To open in terminal instead:
set-work <change-id> --terminal
Close Worktree
set-close <change-id>
Removes the worktree. Interactive mode asks what to do with the branch:
- Keep branch (can reopen later)
- Delete local branch only
- Delete local and remote branch
Non-interactive options:
set-close <change-id> --keep-branch # Keep the branch
set-close <change-id> --delete-remote # Delete both local and remote
Merge Worktree
set-merge <change-id>
Merges the worktree branch into the target branch (default: main).
Options:
set-merge <change-id> --target develop # Merge to specific branch
set-merge <change-id> --no-delete # Keep branch after merge
What ships with it
5 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.
- today First seen · 241 lines · 38 tokens per session scan A 65a5b51230e6
set is a skill published in the GitHub repository tatargabor/set-core (35 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 1,435 once invoked, about $0.0002 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-06.
Other skills, from other repositories
atmos-vendoring
Component vendoring: vendor.yaml and component.yaml manifests, immutable vendor.lock.yaml receipts, pulling from Git/S3/HTTP/OCI/Terraform Registry, --stack/--labels/--tags selector composition, native vendor update, clean, diff, config, and reviewed local component copies.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-git
Atmos Git and GitOps: git.repositories, clone/pull/status/diff/commit/push/clean, local Git hook shims, signed commits, managed workdirs, fork-PR trust gate, and auth via identities or github/sts.
gh-pr-review
Review GitHub Pull Requests using the gh CLI. Use when a user asks to review a PR, perform code review, check a pull request, or provide feedback on proposed changes. Triggers on phrases like "review PR", "review pull request", "check PR", "code review".
hatch3r-issue-workflow
Guides the 8-step agentic development workflow for issues/work items. Covers parsing issues, loading skills, reading specs, planning, implementing, testing, opening PRs/MRs, and addressing review. Use when working on any issue/work item or when the user mentions an issue number.