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 nguyenthanhtat/screen1-claude --skill remotegit clone --depth 1 https://github.com/nguyenthanhtat/screen1-claudeWrote 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/nguyenthanhtat/screen1-claude/remote)<a href="https://agentmods.dev/skills/nguyenthanhtat/screen1-claude/remote"><img src="https://agentmods.dev/badge/skills/nguyenthanhtat/screen1-claude/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/skills/nguyenthanhtat/screen1-claude/remote"><img src="https://agentmods.dev/badge/skills/nguyenthanhtat/screen1-claude/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.00000 | $0.04123 |
| Opus 5 | $0.00000 | $0.02062 |
| Sonnet 5 | $0.00000 | $0.00825 |
| Haiku 4.5 | $0.00000 | $0.00412 |
Grade C, and why
remote scanned grade C with 1 finding 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
ssh-add ~/.ssh/id_ed25519 # Add key to agent How it starts
The opening of the file, as written. The whole thing — 766 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Remote
Parent Skill: /git
Path: /git/remote
Purpose
Master remote repository operations including adding remotes, fetching, pulling, pushing, managing multiple remotes (origin/upstream), and syncing forks.
When to Use
Trigger automatically when:
- User mentions: remote, fetch, push, pull, origin, upstream, fork, sync
- Pushing code to GitHub/GitLab
- Syncing with team repository
- Managing multiple remotes
- Fork synchronization
Chat commands:
/git/remote push my branch to GitHub
/git/remote sync my fork with upstream
/git/remote what's the difference between fetch and pull
/git/remote add upstream repository
/git/remote force push safely
Requirements
Verification
# Check remote configuration
git remote -v
# Test authentication
git ls-remote origin
# Check tracking branches
git branch -vv
Critical Rules
Remote Workflow
Local Repository ←→ Remote Repository (origin)
↑
└─→ Upstream Repository (for forks)
Commands:
fetch: Download changes (don't merge)
pull: Download and merge (fetch + merge)
push: Upload local commits
Patterns
Pattern 1: Add and Remove Remotes
Problem: Connect local repository to remote hosting
# ❌ BAD: Add remote without verification
git remote add origin https://github.com/user/repo.git
# Typo in URL? Won't know until push fails!
# ✅ GOOD: Add remote and verify
git remote add origin [email protected]:user/repo.git
git remote -v # Verify URL
git ls-remote origin # Test connection
# ✅ BETTER: Add with immediate fetch
git remote add origin [email protected]:user/repo.git
git fetch origin
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 · 766 lines · 0 tokens per session scan C 59211cdb711a
remote is a skill published in the GitHub repository nguyenthanhtat/screen1-claude (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,123 tokens. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
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…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.