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 jnPiyush/AgentX --skill remote-git-operationsgit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/jnpiyush/agentx/remote-git-operations)<a href="https://agentmods.dev/skills/jnpiyush/agentx/remote-git-operations"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/remote-git-operations/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/jnpiyush/agentx/remote-git-operations"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/remote-git-operations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 115 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00056 | $0.01491 |
| Opus 5.5 | $0.00022 | $0.00596 |
| Sonnet 5.5 | $0.00011 | $0.00298 |
| Haiku 4.5 | $0.00006 | $0.00149 |
Grade A, and why
remote-git-operations 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 1mo 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remote Git Repository Operations
Purpose: Best practices for working with remote Git repositories, including GitHub, Azure DevOps, GitLab, and Bitbucket.
When to Use This Skill
- Configuring remote Git repositories and authentication
- Managing pull request workflows across platforms
- Resolving conflicts between local and remote branches
- Integrating Git with CI/CD pipelines
- Working with Git LFS for large files
Prerequisites
- Git 2.30+ installed
- Remote repository access (GitHub, Azure DevOps, GitLab, etc.)
Decision Tree
What remote Git operation?
+-- Setting up authentication?
| +-- Personal machine? -> SSH key
| +-- CI/CD pipeline? -> Deploy key or app token
| +-- Temporary access? -> HTTPS + credential helper
+-- Collaborating on code?
| +-- Small team, single remote? -> Feature branch + PR
| +-- Fork-based (open source)? -> Fork + upstream remote + PR
| +-- Multiple remotes? -> Named remotes (origin, upstream)
+-- Syncing with remote?
| +-- Linear history preferred? -> git pull --rebase
| +-- Merge commits acceptable? -> git pull (merge)
| +-- CI branch behind? -> git fetch + git rebase origin/main
+-- Handling large files?
| +-- Binary assets (images, models, videos)? -> Git LFS
| +-- Large repo history? -> Shallow clone (--depth 1)
Remote Repository Setup
Adding and Managing Remotes
# View existing remotes
git remote -v
# Add a new remote
git remote add origin https://github.com/username/repo.git
git remote add upstream https://github.com/original/repo.git
# Change remote URL
git remote set-url origin https://github.com/username/new-repo.git
# Remove a remote
git remote remove upstream
# Rename a remote
git remote rename origin main-repo
# Fetch remote information
git remote show origin
Clone Strategies
# Standard clone
git clone https://github.com/username/repo.git
# Clone with different folder name
git clone https://github.com/username/repo.git my-project
# Clone specific branch
git clone -b develop https://github.com/username/repo.git
# Shallow clone (faster, less history)
git clone --depth 1 https://github.com/username/repo.git
# Clone with submodules
git clone --recursive https://github.com/username/repo.git
# Clone using SSH
git clone [email protected]:username/repo.git
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed 111b6631a842
- 1mo ago First seen · 215 lines · 56 tokens per session scan A ff44d8397cdb
remote-git-operations is a skill published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,491 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…