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.
git clone --depth 1 https://github.com/loulanyue/spec-kit-zhWrote 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/loulanyue/spec-kit-zh/speckit.git.remote)<a href="https://agentmods.dev/commands/loulanyue/spec-kit-zh/speckit.git.remote"><img src="https://agentmods.dev/badge/commands/loulanyue/spec-kit-zh/speckit.git.remote/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/loulanyue/spec-kit-zh/speckit.git.remote"><img src="https://agentmods.dev/badge/commands/loulanyue/spec-kit-zh/speckit.git.remote.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.00008 | $0.00336 |
| Opus 5.5 | $0.00003 | $0.00134 |
| Sonnet 5.5 | $0.00002 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00034 |
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 14d 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.remote — 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.
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:
- Repository owner: Extract from the URL (e.g.,
githubfromhttps://github.com/github/spec-kit.git) - Repository name: Extract from the URL (e.g.,
spec-kitfromhttps://github.com/github/spec-kit.git) - Is GitHub: Whether the remote points to a GitHub repository
Supported URL formats:
- HTTPS:
https://github.com/<owner>/<repo>.git - SSH:
[email protected]:<owner>/<repo>.git
[!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
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.
- 14d ago First seen · 46 lines · 8 tokens per session scan A 00397aff45bf
speckit.git.remote is a command published in the GitHub repository loulanyue/spec-kit-zh (337 stars, last pushed 13d ago), licensed MIT. It adds 8 tokens to every session and 336 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.remote, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
ijfw-ship
Run the IJFW workflow Ship phase (Deep D6). Pre-flight, deploy, and close. Usage: /ijfw-ship.
branch-commit
Return a branch name and concise commit message (max 3 lines) for the current task, grounded in the real git diff; with --apply, create the commit after showing the staged diff. Use when the user only needs quick branch and commit naming before committing, PR packaging is unnecessary, and a real diff exists; use…
approve-proposed
Atomically persist every file marked PROPOSED in the most recent prior assistant turn's ### Artifact changes block, promoting staged content to real files. Invoked on request only. Use when that block contained files marked PROPOSED and you have accepted the inline content of each. Do not use when the prior turn had…
pr-package
Prepare a GitHub PR delivery package (branch, commits, PR title and body, reviewer notes) from the real git diff against an explicit base branch, persisted as PRPACKAGE.md, never inventing work outside the diff. Use when scope is done and diff is stable. Do not use mid-implementation, for a branch name (use…
worktree
Use the superskill worktree MCP tools. Input: $ARGUMENTS (empty = status).
task-workspace
Provision, report, or attach a dedicated git worktree and branch for the active task so parallel tasks do not collide on one working tree. Opt-in, git-gated. Use when a task needs an isolated worktree and branch, or to attach one to an in-flight task. Do not use for the ephemeral slice-level worktrees implement-fleet…