speckit.git.validate

speckit.git.validate is a command for GitHub Copilot from alonf/specrew. It costs 0 tokens per session (10 once invoked), scanned A, a copy of speckit.git.validate, MIT.

A branch-checking command that verifies the current Git branch uses an approved feature naming pattern and has a matching specification folder.

In plain words
What is it for?
Use it to check branch names, find the related folder under specs, and report missing or invalid feature links.
Why use it?
It catches branches that cannot be linked clearly to their feature specifications.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt. Also seen: agent in frontmatter.

Good fit Use it to check branch names, find the related folder under specs, and report missing or invalid feature links.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/alonf/specrew/speckit.git.validate
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.

Clone the repo
git clone --depth 1 https://github.com/alonf/specrew

Made for: GitHub Copilot.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/alonf/specrew/speckit.git.validate/github.svg)](https://agentmods.dev/commands/alonf/specrew/speckit.git.validate)
Your own site
<a href="https://agentmods.dev/commands/alonf/specrew/speckit.git.validate"><img src="https://agentmods.dev/badge/commands/alonf/specrew/speckit.git.validate/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.validate

Your own site · 80×15
<a href="https://agentmods.dev/commands/alonf/specrew/speckit.git.validate"><img src="https://agentmods.dev/badge/commands/alonf/specrew/speckit.git.validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 10 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.00000 $0.00010
Opus 5.5 $0.00000 $0.00004
Sonnet 5.5 $0.00000 $0.00002
Haiku 4.5 $0.00000 $0.00001

Measured 2mo ago against content hash 0f29e55cbfbf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

speckit.git.validate 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 2mo 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.validate — 0 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.

.github/prompts/speckit.git.validate.prompt.md · 4 lines

The source is not reproduced here

Licensed MIT

The repository is licensed MIT, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 2mo ago Changed · -46 lines · -8 tokens per session 0f29e55cbfbf
  2. 2mo ago First seen · 50 lines · 8 tokens per session scan A d8f8e5ecc52e

Subscribe to this mod's changes

speckit.git.validate is a command published in the GitHub repository alonf/specrew (54 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 10 tokens. A static security scan graded it A with 0 findings. It is 100% identical to speckit.git.validate, differing in 0 lines, and is treated as a copy.

Related

speckit.git.validate compared with commands from other repositories

speckit.git.validate next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
speckit.git.validatealonf/specrewCommand54yesterdayMITA0GitHub Copilot
merge-conflict-analysisrjmurillo/ai-agentsCommand49yesterdayMITA0GitHub Copilot
release-notesOpenHands/extensionsCommand176yesterdayMITA44Claude Code
commitechoVic/blade-codeCommand18124d agoMITA8Claude Code
repo-audittractorjuice/arc-kitCommand2.3k2d agononeA29Claude Code
propsmill/infrahub-mcpCommand10yesterdayApache-2.0A18Claude Code
codex-reviewoalders/kitchen-sinkCommand54d agoMITA41Claude Code