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 CodeInfinity1/Stram --skill git-auth-setupgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/git-auth-setup)<a href="https://agentmods.dev/skills/codeinfinity1/stram/git-auth-setup"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/git-auth-setup/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/codeinfinity1/stram/git-auth-setup"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/git-auth-setup.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.00031 | $0.00449 |
| Opus 5.5 | $0.00012 | $0.00180 |
| Sonnet 5.5 | $0.00006 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
git-auth-setup 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.
What it actually says
Git Auth Setup
Purpose
Help the user make Git and GitHub authentication work while keeping credentials private. This skill diagnoses auth state and gives setup steps or runs approved safe commands.
When To Use
Use when clone, fetch, push, gh, SSH, HTTPS token, credential manager, or permission errors block repo work.
Inputs And Evidence
- Error output, remote URL, auth method, platform, and intended operation.
git remote -v,gh auth status, SSH test output, and credential-helper config when approved.
Tool Map
run_shell_commandread_filesystem_statusgithub-repo-management
Workflow
- Identify whether Git uses HTTPS, SSH, or gh auth.
- Inspect non-secret config and current error output.
- Recommend the least invasive fix: gh login, credential-manager refresh, SSH key setup, or remote URL update.
- Never ask the user to paste secrets into chat.
- Run auth commands only when the user approves interactive/setup work.
- Verify with a safe read or status command before retrying the original operation.
Native Implementation Boundaries
- Use native Git/gh/ssh commands through approved shell tooling.
- Do not import external reference auth scripts.
- Do not store tokens in files managed by skills.
Safety And Approval
- Treat tokens, private keys, and credential-helper output as secrets.
- Avoid printing sensitive values.
- Do not change remotes or credential helpers without approval.
Verification
- Auth success should be proven by
gh auth status,ssh -Tstyle output, or a safe Git command. - Push readiness is separate from permission to push.
- Report remaining permission blockers exactly.
Failure Modes
- Exposing a token in logs.
- Fixing the wrong account.
- Retrying pushes without user intent.
References
- Shortlist item:
git-auth-setup. - Native path: GitHub CLI/Git through Stram shell tooling.
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 First seen · 65 lines · 31 tokens per session scan A 80db3ebb0e62
git-auth-setup is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 449 once invoked, about $0.0001 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
omh-deploy-and-monitor
This is an OMH deploy-and-monitor workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
monorepo-navigator
Inspect or improve Turborepo, Nx, pnpm, or Lerna monorepos: package boundaries, dependency graphs, selective tests, caching, and migrations.
ci-cd-ops
CI/CD pipeline patterns with GitHub Actions, release automation, and testing strategies. Use for: github actions, workflow, CI, CD, pipeline, deploy, release, semantic release, changesets, goreleaser, matrix, cache, secrets, environment, artifact, reusable workflow, composite action.