Borrowing it
Nothing to install: this file belongs to alfredoperez/speckit-companion. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/alfredoperez/speckit-companion/main/.specify/extensions/git/commands/speckit.git.feature.mdgit clone --depth 1 https://github.com/alfredoperez/speckit-companionWrote 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/commands/alfredoperez/speckit-companion/speckit.git.feature)<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/speckit.git.feature"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/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.
<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/speckit.git.feature"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/speckit.git.feature.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.00009 | $0.01047 |
| Opus 5.5 | $0.00004 | $0.00419 |
| Sonnet 5.5 | $0.00002 | $0.00209 |
| Haiku 4.5 | $0.00001 | $0.00105 |
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 5d 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
100% identical to speckit.git.feature — 81 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.
How it starts
The opening of the file, as written. The whole thing — 83 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_COMMAND_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--timestampflags are ignoredFEATURE_NUMis extracted when the final path segment starts with a numeric or timestamp feature marker (for example042-name,feat/042-name, orjdoe/app/042-name), 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:
- Check
.specify/extensions/git/git-config.ymlforbranch_numberingvalue - Check
.specify/init-options.jsonforfeature_numberingvalue (inherit from core) - Check
.specify/init-options.jsonforbranch_numberingvalue (deprecated, backward compatibility — will be removed in a future release) - Default to
sequentialif none of the above exist
Branch Name Template
Check .specify/extensions/git/git-config.yml for an optional branch_template value. If it is empty or missing, use the default branch shape {number}-{slug}. If it is set, {slug} must not appear before {number}, its final path segment must start with {number}-, and the script expands these tokens:
{author}: sanitized Git config author (user.name, falling back to the email local part){app}: sanitized Spec Kit init directory name{number}: sequential number or timestamp{slug}: generated short branch slug
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.
- 5d ago Changed · +79 lines · +9 tokens per session f8dec57042b3
- 1mo ago Changed · -64 lines · -9 tokens per session d8b84fd2754b
- 1mo ago First seen · 68 lines · 9 tokens per session scan A facdc68ceff5
speckit.git.feature is a command published in the GitHub repository alfredoperez/speckit-companion (99 stars, last pushed 6d ago), licensed MIT. It adds 9 tokens to every session and 1,047 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to speckit.git.feature, differing in 81 lines, and is treated as a copy.
Other commands, from other repositories
fest-commit
Commit changes with festival traceability metadata.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
mode
Show or switch the project's conformance mode between Enforced and À la carte, within the set the organization allows.
commit-push-pr
Commit, push, and open a PR (includes changeset creation).
util.gh-pr-content
Create pull request content from the current branch changes.
sync-branch
Sync feature branch with the latest main branch.