Seshat-BI: Skill for Claude Code

.claude/skills/speckit-git-feature/SKILL.md

speckit-git-feature is a skill for Claude Code from Kemetra/Seshat-BI. It costs 16 tokens per session (794 once invoked), scanned A, a copy of speckit-git-feature, Apache-2.0.

A tool for creating and switching to a Git feature branch, which is a separate line of development for one change. It can number branches sequentially or use timestamps, and can accept an exact branch name.

In plain words
What is it for?
Starting work on a specified feature in Git, with consistent branch naming based on project configuration or an explicit name.
Why use it?
It removes the repeated manual work of choosing branch names and creating branches consistently. It also checks whether the current folder is a Git repository before creating one.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is Kemetra/Seshat-BI's own configuration. It tells Claude Code how to work on Seshat-BI 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 Seshat-BI configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Kemetra/Seshat-BI. 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/Kemetra/Seshat-BI/main/.claude/skills/speckit-git-feature/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Kemetra/Seshat-BI

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 speckit-git-feature

README.md
[![agentmods](https://agentmods.dev/badge/skills/kemetra/seshat-bi/speckit-git-feature/github.svg)](https://agentmods.dev/skills/kemetra/seshat-bi/speckit-git-feature)
Your own site
<a href="https://agentmods.dev/skills/kemetra/seshat-bi/speckit-git-feature"><img src="https://agentmods.dev/badge/skills/kemetra/seshat-bi/speckit-git-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 speckit-git-feature

Your own site · 80×15
<a href="https://agentmods.dev/skills/kemetra/seshat-bi/speckit-git-feature"><img src="https://agentmods.dev/badge/skills/kemetra/seshat-bi/speckit-git-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 794 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 100% copy Near-identical to another mod 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.00016 $0.00794
Opus 5 $0.00008 $0.00397
Sonnet 5 $0.00003 $0.00159
Haiku 4.5 $0.00002 $0.00079

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

Security

Grade A, and why

speckit-git-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.

Origin

This is a copy

100% identical to speckit-git-feature — 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.

.claude/skills/speckit-git-feature/SKILL.md · 72 lines

How it starts

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

Create Feature Branch

Create and switch to a new git feature branch for the given specification. This command handles branch creation only — the spec directory and files are created by the core /speckit-specify workflow.

User Input

$ARGUMENTS

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

Environment Variable Override

If the user explicitly provided GIT_BRANCH_NAME (e.g., via environment variable, argument, or in their request), pass it through to the script by setting the GIT_BRANCH_NAME environment variable before invoking the script. When GIT_BRANCH_NAME is set:

  • The script uses the exact value as the branch name, bypassing all prefix/suffix generation
  • --short-name, --number, and --timestamp flags are ignored
  • FEATURE_NUM is extracted from the name if it starts with a numeric prefix, otherwise set to the full branch name

Prerequisites

  • Verify Git is available by running git rev-parse --is-inside-work-tree 2>/dev/null
  • If Git is not available, warn the user and skip branch creation

Branch Numbering Mode

Determine the branch numbering strategy by checking configuration in this order:

  1. Check .specify/extensions/git/git-config.yml for branch_numbering value
  2. Check .specify/init-options.json for branch_numbering value (backward compatibility)
  3. Default to sequential if neither exists

Execution

Generate a concise short name (2-4 words) for the branch:

  • Analyze the feature description and extract the most meaningful keywords
  • Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
  • Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)

Run the appropriate script based on your platform:

  • Bash: .specify/extensions/git/scripts/bash/create-new-feature.sh --json --short-name "<short-name>" "<feature description>"
  • Bash (timestamp): .specify/extensions/git/scripts/bash/create-new-feature.sh --json --timestamp --short-name "<short-name>" "<feature description>"
  • PowerShell: .specify/extensions/git/scripts/powershell/create-new-feature.ps1 -Json -ShortName "<short-name>" "<feature description>"
  • PowerShell (timestamp): .specify/extensions/git/scripts/powershell/create-new-feature.ps1 -Json -Timestamp -ShortName "<short-name>" "<feature description>"

Read the full file on GitHub · 72 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 · 72 lines · 16 tokens per session scan A 50a413ca98b6

Subscribe to this mod's changes

speckit-git-feature is a skill published in the GitHub repository Kemetra/Seshat-BI (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 16 tokens to every session and 794 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to speckit-git-feature, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

dbt_ingest

Map dbt schema.yml / properties.yml models and sources into ktx semantic-layer overlays and column notes. Covers sources: vs models:, column datatests (notnull, unique, acceptedvalues, relationships), and how bundle-time writes complement manifest backfill from git sync. Load when the WorkUnit's skillNames includes…

Kaelio/ktx · 103 tokens

release_notes_generator

Skill "release_notes_generator" from G-Schumacher44/strata-oss, covering skill: releasenotesgenerator, trigger, inputs, allowed tools and forbidden.

G-Schumacher44/strata-oss · 0 tokens

github

Skill "github" from clawdata/clawdata, covering github, authentication, commands, repositories and issues.

clawdata/clawdata · 0 tokens

ktx-analytics

Use when answering a question that needs data from a ktx-connected database - investigating, analyzing, "how many", "show me", "what's the breakdown of", finding records by value, exploring tables, comparing periods, explaining metrics, or any data-analysis request. Triggers even when the user does not say…

Kaelio/ktx · 86 tokens

metabase_ingest

Convert Metabase questions, models, and metrics into ktx Semantic Layer source definitions. Covers result-metadata to KSL column type mapping, FK/PK detection, near-duplicate deduplication, pre-aggregation decomposition, join-graph connectivity, and how to react to priorProvenance from earlier ingest syncs. Load when…

Kaelio/ktx · 90 tokens

sl_capture

How to capture new reusable patterns into ktx's semantic layer - when a measure, segment, or join belongs in the catalog and how to write it generically so it stays small and useful over time. Loaded by the post-turn memory-agent only. The research agent does not write to the SL.

Kaelio/ktx · 63 tokens