autospec: Skill for Claude Code

.agents/skills/autospec-worktree-setup/SKILL.md

autospec-worktree-setup is a skill for Claude Code from ariel-frischer/autospec. It costs 19 tokens per session (1,532 once invoked), scanned A, original, MIT.

A tool that creates a project-specific setup script for Git worktrees, which are separate working copies of one repository.

In plain words
What is it for?
Use it to analyze a project, identify its package manager from lockfiles and project files, copy needed configuration, and prepare new Git worktrees.
Why use it?
It avoids manually figuring out which configuration files to copy and which package-install commands to run when starting another worktree.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; positional $N argument; mentions Claude Code.

This is ariel-frischer/autospec's own configuration. It tells Claude Code how to work on autospec itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything autospec configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ariel-frischer/autospec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ariel-frischer/autospec/main/.agents/skills/autospec-worktree-setup/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ariel-frischer/autospec

Made for: Claude Code.

Wrote 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.

agentmods badge for autospec-worktree-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/ariel-frischer/autospec/autospec-worktree-setup/github.svg)](https://agentmods.dev/skills/ariel-frischer/autospec/autospec-worktree-setup)
Your own site
<a href="https://agentmods.dev/skills/ariel-frischer/autospec/autospec-worktree-setup"><img src="https://agentmods.dev/badge/skills/ariel-frischer/autospec/autospec-worktree-setup/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.

agentmods 80×15 button for autospec-worktree-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/ariel-frischer/autospec/autospec-worktree-setup"><img src="https://agentmods.dev/badge/skills/ariel-frischer/autospec/autospec-worktree-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,532 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Agent Snooping · line 115
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.01532
Opus 5 $0.00010 $0.00766
Sonnet 5 $0.00004 $0.00306
Haiku 4.5 $0.00002 $0.00153

Measured 9d ago against content hash ed7263edaed7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

autospec-worktree-setup 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 9d 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.

.agents/skills/autospec-worktree-setup/SKILL.md · 163 lines

How it starts

The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.

autospec-worktree-setup

This Agent Skill is generated from autospec.worktree-setup. When the user invokes "$autospec-worktree-setup" or "/autospec.worktree-setup", load and follow these instructions directly. Treat the text after the skill or command name as "$ARGUMENTS". Do not route back through "autospec worktree-setup"; this skill is the prompt for the stage.

Project specs directory: ./specs

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

You are generating a project-specific setup script that will be run when creating new git worktrees. This script handles copying essential configuration files and running package manager install commands instead of copying large dependency directories.

Follow this execution flow:

  1. Analyze project structure:
    • Identify package managers by checking for lockfiles:

      • package-lock.json -> npm
      • yarn.lock -> yarn
      • pnpm-lock.yaml -> pnpm
      • bun.lockb -> bun
      • go.sum or go.mod -> go
      • requirements.txt or Pipfile.lock -> pip/pipenv
      • poetry.lock or pyproject.toml with [tool.poetry] -> poetry
      • Cargo.lock -> cargo
      • Gemfile.lock -> bundler
      • composer.lock -> composer
    • Identify essential directories/files to copy:

      Autospec-related (REQUIRED for autospec workflows):

      • .autospec/ - Contains constitution, config, memory, and generated scripts. The constitution.yaml is REQUIRED for all workflow stages (specify, plan, tasks, implement).
      • .agents/skills/ (if exists) - Shared autospec skills for Codex and OpenCode skill-aware sessions.
      • .claude/skills/ (if exists) - Claude Code project skills. Required if using agent_preset: claude.
      • opencode.json (if exists) - OpenCode configuration file with permissions and model settings. Located at project root, not inside .opencode/.

      IDE/Editor configuration:

      • .vscode/ (if exists)
      • .idea/ (if exists)
      • Other gitignored config directories needed for development
    • Identify files/directories to EXCLUDE:

      • Dependency directories: node_modules/, vendor/, __pycache__/, .venv/, venv/, target/, dist/, build/, .bundle/
      • Generated files: *.log, *.tmp, .cache/, coverage/

Read the full file on GitHub · 163 lines

Changes

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.

  1. 9d ago First seen · 163 lines · 19 tokens per session scan A ed7263edaed7

Subscribe to this mod's changes

autospec-worktree-setup is a skill published in the GitHub repository ariel-frischer/autospec (141 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 1,532 once invoked, about $0.0001 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-08-30.

Related

Other skills, from other repositories

release

Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.

jrswab/axe · 30 tokens

commit-msg

You receive a git diff of staged changes via stdin. Generate a commit message.

jrswab/axe · 0 tokens

approve-proposed

Atomically persist every file marked PROPOSED in the most recent prior assistant turn's ### Artifact changes block. Single-command idiom that closes the two-step latency in ADR-0001's PROPOSED-by-default contract; the user reviews proposals in Ask/Plan mode, then runs this once to write all of them. Use when the prior…

Mozurok/fhorja.dev · 161 tokens

reconcile-worktrees

Safely consolidate one or more isolated git worktrees (for example left behind by parallel background agents, or from the fix-batch skill) into the main working tree, without committing or merging blindly. Use whenever asked to "reconcile the worktrees", "merge these agent branches", "bring the worktree changes back…

hams-ollo/zen-agent-skills · 161 tokens

gh-pr-review

View and manage inline GitHub PR review comments with full thread context from the terminal.

agynio/gh-pr-review · 20 tokens

branch-commit

Return a branch name and a concise commit message (at most 2 lines) for the current task, grounded in the real git diff rather than a paraphrase of the task summary, and with --apply optionally create that commit after showing it and getting the user's confirmation in the same turn. Use when the user only needs quick…

Mozurok/fhorja.dev · 193 tokens