speckit.git.remote

A command that reads a project's Git remote URL and determines whether it points to GitHub, an online service for hosting Git repositories and collaborating on code.

In plain words
What is it for?
Use it when another command needs the GitHub owner and repository name, such as for creating issues.
Why use it?
It avoids guessing the repository location and handles cases where Git, a repository, or a remote is missing.

Command

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 commands/github/spec-kit/speckit.git.remote
Clone the repo
git clone --depth 1 https://github.com/github/spec-kit
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 336 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00008 $0.00336
Opus 5 $0.00004 $0.00168
Sonnet 5 $0.00002 $0.00067
Haiku 4.5 $0.00001 $0.00034

Measured yesterday against content hash 00397aff45bf, 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.remote 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 yesterday.

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

Copies of this mod

8 near-identical copies found in the catalogue:

extensions/git/commands/speckit.git.remote.md · 46 lines

What it actually says

Detect Git Remote URL

Detect the Git remote URL for integration with GitHub services (e.g., issue creation).

Prerequisites

  • Check if Git is available by running git rev-parse --is-inside-work-tree 2>/dev/null
  • If Git is not available, output a warning and return empty:
    [specify] Warning: Git repository not detected; cannot determine remote URL
    

Execution

Run the following command to get the remote URL:

git config --get remote.origin.url

Output

Parse the remote URL and determine:

  1. Repository owner: Extract from the URL (e.g., github from https://github.com/github/spec-kit.git)
  2. Repository name: Extract from the URL (e.g., spec-kit from https://github.com/github/spec-kit.git)
  3. Is GitHub: Whether the remote points to a GitHub repository

Supported URL formats:

[!CAUTION] ONLY report a GitHub repository if the remote URL actually points to github.com. Do NOT assume the remote is GitHub if the URL format doesn't match.

Graceful Degradation

If Git is not installed, the directory is not a Git repository, or no remote is configured:

  • Return an empty result
  • Do NOT error — other workflows should continue without Git remote information
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. yesterday First seen · 46 lines · 8 tokens per session scan A 00397aff45bf

Subscribe to this mod's changes

speckit.git.remote is a command published in the GitHub repository github/spec-kit (132,298 stars, last pushed 3d ago), licensed MIT. It adds 8 tokens to every session and 336 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-08-30.

Related

Other commands, from other repositories