speckit.git.feature

Create a feature branch with sequential or timestamp numbering.

Agent

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.

agentmods
npx agentmods add agents/snowdreamtech/template/speckit.git.feature
Clone the repo
git clone --depth 1 https://github.com/snowdreamtech/template
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 764 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00009 $0.00764
Opus 5 $0.00005 $0.00382
Sonnet 5 $0.00002 $0.00153
Haiku 4.5 $0.00001 $0.00076

Measured today against content hash d70dee326189, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

.github/agents/speckit.git.feature.agent.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 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 · 76 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. today First seen · 76 lines · 9 tokens per session scan A d70dee326189

Subscribe to this mod's changes

speckit.git.feature is an agent published in the GitHub repository snowdreamtech/template (15 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 764 once invoked, about $0.0000 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-01.

Related

Other agents, from other repositories

content-reviewer

Audit conformite du contenu public. Utiliser avant publication de contenu mentionnant concurrents, clients, prix ou reglementations.

stoa-platform/stoa · 30 tokens

qa-agent

Agent name: QA-Agent Role: QA Lead — full audit OR Orchestrator close-loop verification Human equivalent: QA Lead Classification: Agent (stateful, reasoning, governed) Trust tier at introduction: PROVISIONAL (nsessions < 5) Install: Copy this file to .claude/commands/qa-agent.md in your repo. Invoke with /qa-agent for…

rayyagari2-create/agentic-workforce-framework · 0 tokens

marketing-strategist

Marketing strategy, positioning, copywriting, SEO, CRO, and content creation. Works as a peer to the PM — not a subordinate. Gives the product/market direction while the PM gives the technical direction. Use PROACTIVELY when: working on landing pages, pricing pages, social media posts, email sequences, SEO…

rbah31/claude-code-workflow · 173 tokens

strategic-qa

Tech Lead and QA reviewer for autonomous sprint orchestration. Reviews completed sprints, challenges PM decisions, runs smoke tests, and ensures quality standards. Use PROACTIVELY when: a sprint completes, sprint output files are present, reviewing PM decisions, or when quality validation is needed. Also use when the…

rbah31/claude-code-workflow · 114 tokens

security-auditor

Application security auditor and red team specialist. Use when reviewing auth/authorization, billing/payment, data handling, internet-exposed endpoints, cryptographic operations, or any security-sensitive code.

rbah31/claude-code-workflow · 41 tokens

Claude Code CLAUDE.md Template

프로젝트 루트에 CLAUDE.md를 두면 Claude Code가 매 세션 시작 시 자동 로드한다. Codex의 /.codex/AGENTS.md + 프로젝트 AGENTS.md, Cursor의 .cursor/rules/.mdc와 동등한 역할.

szara7678/OpenAkashic · 0 tokens