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 rahmanef63/si-coder-agent --skill sc-gitgit clone --depth 1 https://github.com/rahmanef63/si-coder-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/rahmanef63/si-coder-agent/sc-git)<a href="https://agentmods.dev/skills/rahmanef63/si-coder-agent/sc-git"><img src="https://agentmods.dev/badge/skills/rahmanef63/si-coder-agent/sc-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/rahmanef63/si-coder-agent/sc-git"><img src="https://agentmods.dev/badge/skills/rahmanef63/si-coder-agent/sc-git.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium Excessive Agency · line 77 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 136 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00111 | $0.02858 |
| Opus 5.5 | $0.00044 | $0.01143 |
| Sonnet 5.5 | $0.00022 | $0.00572 |
| Haiku 4.5 | $0.00011 | $0.00286 |
Grade A, and why
sc-git scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
6. **`gh` CLI, not raw curl**: reuse the existing `gh` auth + scopes. Fall back to `gh api` for endpoints without dedicated subcommands. How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc-git — GitHub Actions Replacement & Repo CRUD
Use when user wants to stop GitHub Actions cloud minutes burn, audit workflow files across your repos, migrate CI/CD to pre-push hooks + VPS, or do generic repo/workflow CRUD via gh API.
Connection-safe provider execution
Git/GitHub operations that need the selected SI-Coder GitHub credential should run through sc run -- ... when using a direct named connection. Credential-free local audits/CI helpers may run directly. Never export the PAT globally just to make a helper work.
Pre-requisites
ghCLI authed withrepo+workflow+admin:repo_hookscopes- Local clones live in
~/projects/<repo>(override withPROJECTS_DIR) (some repos remote-only — skill handles both) - your VPS (set
SC_GIT_VPS_HOST) accessible via SSH for runner/cron subcommands
CORE RULES
- Never destructive without backup: before patching any
.github/workflows/*.yml, copy to*.yml.bak. Never delete.bakfiles. - Never force-push, never push directly to main: all changes land via new branch
chore/reduce-github-actions-usage. PR is user's call. - Never touch secrets / env / deploy targets: skill only edits triggers (
on:),concurrency:,paths:. Leavesenv:,secrets:,runs-on:, job steps alone unless explicitly told. - Never run failing workflows on cloud: when listing recent runs, do not retrigger.
- Self-hosted runner only on private repos: GitHub strongly recommends. If all your active repos are private, this is safe. Refuse runner setup if target repo
isPrivate === false. ghCLI, not raw curl: reuse the existingghauth + scopes. Fall back togh apifor endpoints without dedicated subcommands.- Idempotent: re-running
disableon already-disabled workflow is a no-op (detect existingworkflow_dispatch:only + nopush:/pull_request:/schedule:).
Scripts
audit.js — Sweep + report
Scans all your repos, lists workflows, recent run volume, identifies burn risks.
What ships with it
11 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.
- scripts/_shared.js 10 KB runs code
- scripts/audit.js 3.6 KB runs code
- scripts/ci.js 2.8 KB runs code
- scripts/convex-deploy.js 8.7 KB runs code
- scripts/cron.js 2.8 KB runs code
- scripts/disable.js 7.0 KB runs code
- scripts/hook.js 3.2 KB runs code
- scripts/nuke.js 787 B runs code
- scripts/runner.js 3.7 KB runs code
- scripts/status.js 823 B runs code
- scripts/webhook.js 2.7 KB runs code
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 · +10 lines eec41eb6e629
- 1mo ago First seen · 185 lines · 111 tokens per session scan A c0a71d42eb9e
sc-git is a skill published in the GitHub repository rahmanef63/si-coder-agent (13 stars, last pushed 3d ago), licensed MIT. It adds 111 tokens to every session and 2,858 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
bitbucket-workflow
Bitbucket best practices for pull requests, Pipelines CI/CD, Jira integration, and Atlassian ecosystem workflows.
gitlab-workflow
GitLab best practices for merge requests, CI/CD pipelines, issue tracking, and DevOps workflows.
pdlc-ship
A software release workflow that runs tests, updates the version and change log, creates a Git tag, and starts CI/CD, the automated build and deployment process.
github-actions
Designs and hardens GitHub Actions CI/CD - pipelines that hit a sub-10-minute PR feedback budget through caching and parallelism, with least-privilege security and safe deploy gates. Use when someone asks "why is my CI so slow", "how do I cache nodemodules properly", "set up a deploy workflow", "is pullrequesttarget…
check-dependabot
Validate a Dependabot configuration against the published JSON Schema and audit its groups against the repository's real dependency manifests. Use when creating or rewriting .github/dependabot.yml, when adding or reorganising groups, ignore or exclude-patterns, when a dependency lands in the wrong grouped PR or keeps…
monitor-ci
Drive a long-running GitHub Actions run to a trustworthy conclusion without burning the session on polling. Use when asked to wait for a pipeline, watch a build, babysit a release or deploy run, restart it if it fails, or report whether it went green. Also use when a run must finish before a follow-up step such as a…