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 skills add sgaunet/claude-plugins --skill detect-repo-hostgit clone --depth 1 https://github.com/sgaunet/claude-pluginsWrote 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/sgaunet/claude-plugins/detect-repo-host)<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/detect-repo-host"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/detect-repo-host/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/skills/sgaunet/claude-plugins/detect-repo-host"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/detect-repo-host.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.02860 |
| Opus 5 | $0.00021 | $0.01430 |
| Sonnet 5 | $0.00008 | $0.00572 |
| Haiku 4.5 | $0.00004 | $0.00286 |
Grade A, and why
detect-repo-host 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detect Repository Host Skill
Detect the repository hosting service from git remote configuration and extract structured metadata for platform-aware command routing.
Overview
Many commands need to determine whether the current repository is hosted on GitHub, GitLab, or Forgejo to route CLI calls correctly. This skill centralizes that detection logic so commands can invoke it via the Skill tool instead of duplicating git remote -v parsing.
When to Use
- Before calling GitHub, GitLab, or Forgejo CLI tools that require
owner/repoorproject_path - When a command needs to branch logic based on hosting platform
- Any workflow requiring platform-aware routing
Workflow
Step 1: Read Git Remotes
git remote -v
Parse the output to find the origin remote. If origin is not set, prefer a remote named upstream before falling back to the first available one, and say which one you picked.
Step 2: Parse Remote URL
Support both SSH and HTTPS URL formats:
SSH formats (scp-style):
[email protected]:owner/repo.git
[email protected]:group/subgroup/project.git
[email protected]:group/project.git
[email protected]:owner/repo.git
SSH formats (ssh:// scheme, may include a custom port):
ssh://[email protected]/owner/repo.git
ssh://[email protected]:2222/sylvain/mountain-blog-test.git
HTTPS formats:
https://github.com/owner/repo.git
https://gitlab.com/group/subgroup/project.git
https://gitlab.self-hosted.example.com/group/project.git
https://git.sylvlab.fr/owner/repo.git
Parsing rules:
- Strip trailing
.gitsuffix if present - Strip a trailing
/if present. Do this before splitting path segments — otherwise.../group/project/yields an empty last segment andrepocomes back blank. - Extract hostname from URL:
- scp-style (
[user@]host:path): hostname is between@(if present) and the first:. ssh://[user@]host[:port]/path: strip thessh://scheme and anyuser@, then the hostname is up to the next/or:— drop the:<port>segment (e.g.:2222); it is not part of the path.https://[user[:password]@]host/path: drop thehttps://scheme, then take everything up to the first/as the authority. If the authority contains@, keep only what follows the last@— credentials are not part of the hostname. This matters for tokenised CI remotes such ashttps://x-access-token:[email protected]/owner/repo.git, which otherwise produce the hostnamex-access-token:[email protected]and fail the platform lookup in Step 3. Drop a:<port>suffix here too.
- scp-style (
- Extract path segments after the hostname (after the
:for scp-style, after the host[:port] forssh://, after the host for HTTPS). The port number is never an owner/path segment.
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.
- 9d ago First seen · 260 lines · 42 tokens per session scan A 76c25efa2ac7
detect-repo-host is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 7d ago), licensed MIT. It adds 42 tokens to every session and 2,860 once invoked, about $0.0002 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.
Other skills, from other repositories
review-pr
Review a Pull Request in one of two postures: an expository "tour guide" that walks through changes in logical order, or an adversarial audit that assumes the change is wrong until proven safe and hunts for the failure mode. Triggers: "review PR #123", "adversarial review", "walk me through this PR", "PR tour guide"…
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
version-bump
This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository.
commit-message
Use ANY time the user signals they want to commit staged changes — including bare "commit", "/commit", "commit this", "commit these changes", "let's commit", "make a commit", "git commit", "write a commit message", "make a conventional commit", "use conventional commits", or any equivalent phrasing in context (e.g.…
spring-clean
Deep-clean and simplify a whole repo or codebase, then leave guardrails so it stays clean. Delete dead surfaces, gitignore build artifacts, relocate dev docs, notes, clones and dumps to the project's workspace repo (the assistant-dev home base), split oversized files and functions, unify duplicated logic, draw package…