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.
npx agentmods add skills/open-software-network/os-clovy/speckit-git-remotenpx skills add open-software-network/os-clovy --skill speckit-git-remotegit clone --depth 1 https://github.com/open-software-network/os-clovyWrote 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/skills/open-software-network/os-clovy/speckit-git-remote)<a href="https://agentmods.dev/skills/open-software-network/os-clovy/speckit-git-remote"><img src="https://agentmods.dev/badge/skills/open-software-network/os-clovy/speckit-git-remote.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00382 |
| Opus 5 | $0.00008 | $0.00191 |
| Sonnet 5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
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 4d 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.
- 4d ago First seen · 50 lines · 16 tokens per session scan A 045d34977a70
speckit-git-remote is a skill published in the GitHub repository open-software-network/os-clovy (357 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 382 once invoked, about $0.0001 per session on Opus 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 skills, from other repositories
personal-commands
Edit hex.config.ts, not .hex-sdk. Config and installed dependencies execute with the user's normal permissions; use only trusted packages and avoid network, filesystem, environment, or subprocess access unless the requested command requires it. Run bun run check after editing.
hex-personal-commands
Configure HEX personal voice commands, voice-dictation control phrases, and deterministic transcript transformations. Use when the user wants to add or change commands or transformations for the HEX macOS voice app.
macparakeet-stt
Use when the user asks to transcribe audio or video, inspect or manage MacParakeet meeting recordings, search prior dictations/transcripts, or give an AI agent local speech-to-text tools on Apple Silicon.
verify-dictation
The canonical "prove VZT Flow actually works" checklist — the human hotkey test plus its automated equivalents. Use before claiming a dictation-pipeline change works, before a release, or when the user runs /verify-dictation.
release-murmur
Cut a signed, notarized macOS release of Murmur (Tauri 2 + Angular 22). The exact, proven step-by-step runbook — preflight gates → version bump (+ Cargo.lock sync) → JakubGawr commit → PR-merge to the murmur trunk (never direct-push) → rustup targets → stop dev → universal build → Developer-ID sign BY IDENTITY HASH…
ship-feature
Ship a Murmur feature through scope, isolated implementation, fresh adversarial and required security review, project gates, a JakubGawr commit, and a PR to murmur. Use the verifier-only Harness for risky, multi-step, or explicitly requested work; ordinary low-risk fixes keep the normal isolated-worktree route.