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 steph-dove/klaussy-agents --skill httpx-new-worktreegit clone --depth 1 https://github.com/steph-dove/klaussy-agentsWrote 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/steph-dove/klaussy-agents/httpx-new-worktree)<a href="https://agentmods.dev/skills/steph-dove/klaussy-agents/httpx-new-worktree"><img src="https://agentmods.dev/badge/skills/steph-dove/klaussy-agents/httpx-new-worktree/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/steph-dove/klaussy-agents/httpx-new-worktree"><img src="https://agentmods.dev/badge/skills/steph-dove/klaussy-agents/httpx-new-worktree.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.00059 | $0.00411 |
| Opus 5 | $0.00030 | $0.00205 |
| Sonnet 5 | $0.00012 | $0.00082 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
httpx-new-worktree 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 12d 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.
This is a copy
94% identical to fastapi-new-worktree — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Create a new git worktree for the task the user described.
- Read CLAUDE.md to understand the project structure and branching conventions.
- Create a short, descriptive branch name based on the task (e.g.
fix/login-redirect,feat/add-search). - Take the current repository's folder name (you already know the working directory — don't compute it with a shell substitution like
$(basename $PWD), which isn't portable to Windows shells), then rungit worktree add ../<repo-folder>-<branch-name> -b <branch-name> masterto create the worktree from the configured base branch (the trailing start-point keeps the new branch from inheriting whatever branch the user is currently checked out on). - Confirm the worktree was created successfully with
git worktree list. - Tell the user the full path to the new worktree so they can open it.
Rules:
- Always branch from master unless told otherwise.
- Use lowercase kebab-case for branch names.
- Prefix with
fix/,feat/,chore/,docs/, orrefactor/as appropriate. - Do not start work in the worktree — just create it and report the path.
When NOT to use
- The user just wants a new branch in the current working tree (
git checkout -b) — worktrees are for parallel checkouts, not branch creation alone. - A worktree for the same branch already exists — surface the existing path; don't create a duplicate.
- The user is on a non-worktree-friendly hosting setup (some submodule-heavy repos break with worktrees) — flag the risk before creating.
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.
- 12d ago First seen · 25 lines · 59 tokens per session scan A a526ad7ea4d9
httpx-new-worktree is a skill published in the GitHub repository steph-dove/klaussy-agents (16 stars, last pushed 15d ago), licensed MIT. It adds 59 tokens to every session and 411 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to fastapi-new-worktree, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
gh-skill
Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
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.
conventional-commit
Conventional Commit - Generate Conventional Commits 1.0.0 compliant messages. MANDATORY for all git commits. Invoke when user says 'commit', 'commit this', or asks to commit code.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.