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 sdcorejs/sdcorejs-agent --skill sdcorejs-gitgit clone --depth 1 https://github.com/sdcorejs/sdcorejs-agentWrote 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/sdcorejs/sdcorejs-agent/sdcorejs-git)<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-git"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-git/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/sdcorejs/sdcorejs-agent/sdcorejs-git"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-git.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.00083 | $0.05212 |
| Opus 5.5 | $0.00033 | $0.02085 |
| Sonnet 5.5 | $0.00017 | $0.01042 |
| Haiku 4.5 | $0.00008 | $0.00521 |
Grade A, and why
sdcorejs-git 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 16d 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 — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Path resolution: Resolve ../../_refs/... relative to this SKILL.md. Resolve another SDCoreJS skill by opening the sibling folder ../<skill-name>/SKILL.md.
Git
Purpose
One skill for Git artifacts:
- create a scoped Conventional Commit
- push a verified branch
- open or update a pull request
- write release notes or CHANGELOG entries
Readiness and final delivery gates live in sdcorejs-ship.
sdcorejs-git creates artifacts only. It is not the readiness gate, it must not
repair source files, and it must not create commits, pushes, or PRs as a
substitute for verification.
Shared Protocols
Read ../../_refs/shared/runtime-protocols.md. Apply
../../_refs/shared/artifact-lifecycle.md and run SDCoreJS Artifact Closure before staging, commit, or push. For multiple worktrees, nested repositories, or
submodules, load ../../_refs/shared/git-closure-contract.mjs; it verifies approved artifacts, emits exact repository-local path sets, and delegates freshness to
../../_refs/shared/convergence-contract.mjs#evaluateConvergenceHandoff with its verified receipt.
Mode Selection
| Mode | Trigger examples | Output |
|---|---|---|
commit |
"commit", "commit changes", "save changes" | one scoped Conventional Commit |
pr |
"create PR", "open PR", "gh pr create", "PR text" | pushed current branch plus PR URL or local PR draft |
changelog |
"write changelog", "update CHANGELOG", "release notes", "what changed since vX.Y.Z" | Keep a Changelog entry plus semver recommendation |
If multiple modes match, choose the narrowest explicit artifact request:
commit, pr, and changelog are artifact modes; readiness,
delivery, dependency updates, release readiness, and "is this ready" belong to
sdcorejs-ship.
An explicit worktree/isolation request is not an artifact mode. Forward it to
the canonical workspace.isolate owner in
../../_refs/orchestration/workspace-isolation.md, then return the resulting
workspace identity to the execution caller. Do not perform commit, PR, push, or
changelog work during that handoff.
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.
- 16d ago Changed · +2 lines 26d5eeafdc7c
- 25d ago Changed · +3 lines b8ffb5e60f90
- 1mo ago Changed · -6 lines · +2 tokens per session 607c02a2ed7b
- 2mo ago First seen · 502 lines · 81 tokens per session scan A efd09b3df81f
sdcorejs-git is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 83 tokens to every session and 5,212 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
git-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.