horka-git-new-feature

horka-git-new-feature is a skill for Claude Code from joey-barbier/ClaudeCode-Plugin. It costs 62 tokens per session (508 once invoked), scanned A, original, MIT.

A skill that prepares a Git repository for starting a new feature by checking out the main development branch, updating it, cleaning up merged branches, and checking the working tree.

In plain words
What is it for?
Use it before beginning a new feature to make sure the base branch is current and the repository is ready for work.
Why use it?
It reduces mistakes caused by starting from an outdated branch or leaving uncommitted changes in the way.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the horka-dev-workflow plugin — 2 skills, 1 agent, 1 hook shipped together

Good fit Use it before beginning a new feature to make sure the base branch is current and the repository is ready for work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/joey-barbier/claudecode-plugin/horka-git-new-feature
Install

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.

Any agent
npx skills add joey-barbier/ClaudeCode-Plugin --skill horka-git-new-feature
Clone the repo
git clone --depth 1 https://github.com/joey-barbier/ClaudeCode-Plugin

Made for: Claude Code.

Or install horka-dev-workflow, the plugin that ships this one along with the rest of its 2 skills, 1 agent, 1 hook.

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 horka-git-new-feature

README.md
[![agentmods](https://agentmods.dev/badge/skills/joey-barbier/claudecode-plugin/horka-git-new-feature/github.svg)](https://agentmods.dev/skills/joey-barbier/claudecode-plugin/horka-git-new-feature)
Your own site
<a href="https://agentmods.dev/skills/joey-barbier/claudecode-plugin/horka-git-new-feature"><img src="https://agentmods.dev/badge/skills/joey-barbier/claudecode-plugin/horka-git-new-feature/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 horka-git-new-feature

Your own site · 80×15
<a href="https://agentmods.dev/skills/joey-barbier/claudecode-plugin/horka-git-new-feature"><img src="https://agentmods.dev/badge/skills/joey-barbier/claudecode-plugin/horka-git-new-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 508 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.
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.00062 $0.00508
Opus 5 $0.00031 $0.00254
Sonnet 5 $0.00012 $0.00102
Haiku 4.5 $0.00006 $0.00051

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

Security

Grade A, and why

horka-git-new-feature 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.

plugins/horka-dev-workflow/skills/horka-git-new-feature/SKILL.md · 79 lines

What it actually says

New Feature (GNF)

Prepare the git environment for starting a new feature.

Scope

Prepares git environment only. Does NOT:

  • Create feature implementations
  • Modify existing code
  • Push to remote (only local branch operations)

Steps

1. Identify and switch to base branch

git branch -a

Look for develop, main, or master (in that priority order), then checkout:

git checkout <base-branch>

2. Pull latest

git pull origin <base-branch>

If pull has merge conflicts: "Merge conflicts detected on <base-branch>. Resolve them before starting a new feature, or stash your changes and retry."

3. Clean up merged branches

git branch --merged <base-branch> | grep -v "^\*" | grep -vE "^[[:space:]]*(main|master|develop)$"

If merged branches exist, ask: "These branches are already merged and can be deleted: [list]. Delete them?"

4. Confirm ready state

git status

If uncommitted changes: "You have uncommitted changes. Stash them (git stash), commit them, or discard them before proceeding?"

Output:

Environment ready for new feature.
Branch: <base-branch> (up to date)
Working tree: clean

What's the new feature? I'll create the branch: feature/<description>

5. Create feature branch

Wait for user to describe the feature. Sanitize the name (lowercase, hyphens, no special chars):

git checkout -b feature/<sanitized-description>

Error Handling

  • Network/auth failure on pull: "Could not pull latest. Continue on local state or fix connection?"
  • Branch already exists: "Branch feature/X already exists. Switch to it or pick a new name?"
  • Detached HEAD state: Warn and switch to base branch first
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 · 79 lines · 62 tokens per session scan A 20d2cadfe03c

Subscribe to this mod's changes

horka-git-new-feature is a skill published in the GitHub repository joey-barbier/ClaudeCode-Plugin (22 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 508 once invoked, about $0.0003 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

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens