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 NPC-Worldwide/npcsh --skill git-workflowgit clone --depth 1 https://github.com/NPC-Worldwide/npcshWrote 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/npc-worldwide/npcsh/git-workflow)<a href="https://agentmods.dev/skills/npc-worldwide/npcsh/git-workflow"><img src="https://agentmods.dev/badge/skills/npc-worldwide/npcsh/git-workflow/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/npc-worldwide/npcsh/git-workflow"><img src="https://agentmods.dev/badge/skills/npc-worldwide/npcsh/git-workflow.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.00000 | $0.00375 |
| Opus 5.5 | $0.00000 | $0.00150 |
| Sonnet 5.5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
git-workflow 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-workflow
Git workflow best practices. Use when asked about git branching, commits, or merge strategy. [Sections: branching, commits, merging, hotfix]
Branching
Use feature branches off main/develop: git checkout -b feature/my-feature develop Name branches descriptively: feature/ — new functionality fix/ — bug fixes chore/ — maintenance, deps, config Keep branches short-lived. Rebase onto target before merging.
Commits
Write clear commit messages: Line 1: imperative summary under 72 chars Line 3+: explain WHY, not what (the diff shows what) One logical change per commit. Don't mix refactors with features. Use conventional commits if the project uses them: feat: add user search fix: handle null avatar URL chore: bump eslint to v9
Merging
Prefer squash merges for feature branches (clean history). Use merge commits for long-lived branches (preserves context). Always pull/rebase before merging to avoid unnecessary merge commits. Delete branches after merging. Run CI before merging — never merge a red build.
Hotfix
For urgent production fixes:
- Branch off main: git checkout -b hotfix/fix-name main
- Make the minimal fix
- Test thoroughly
- Merge to main AND develop/release
- Tag the release Keep hotfix scope minimal — fix only the immediate issue.
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 · 53 lines · 0 tokens per session scan A 33643ad9f984
git-workflow is a skill published in the GitHub repository NPC-Worldwide/npcsh (495 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 375 tokens. 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.