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 agentmods add skills/vikasudasi/skill-vault/github-actions-cinpx skills add vikasudasi/skill-vault --skill github-actions-cigit clone --depth 1 https://github.com/vikasudasi/skill-vaultWrote 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/vikasudasi/skill-vault/github-actions-ci)<a href="https://agentmods.dev/skills/vikasudasi/skill-vault/github-actions-ci"><img src="https://agentmods.dev/badge/skills/vikasudasi/skill-vault/github-actions-ci.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.01012 |
| Opus 5 | $0.00015 | $0.00506 |
| Sonnet 5 | $0.00006 | $0.00202 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
github-actions-ci 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 3d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Continuous Integration
Use when wiring a repo so every push/PR runs lint, type-check, format-check, and
tests — and blocks merge when they fail. This is exactly what Skill Vault's own
CI does: test, ruff check, mypy, and ruff format --check running as a
pre-merge gate.
Anatomy
name: CI
on:
push:
branches: [main]
pull_request:
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: "3.11"
cache: "pip"
- run: pip install -e ".[dev]"
- run: pytest
ondefines triggers: push to main, every PR,schedulefor cron.- Each
jobruns on its own fresh runner — share nothing between jobs; combine steps that need the same environment.
Checkout + setup-python caching
actions/checkout@v4 fetches the repo. setup-python with cache: "pip" caches
the pip download cache/Ci keyed to your lockfile, cutting install time. Pin
action versions by tag (@v4) or, for supply-chain rigor, by SHA.
The quality gate
Structure the gate so a single failed check blocks merge (protect the branch with "Require status checks to pass before merging"):
| step | command | failure meaning |
|---|---|---|
| lint | ruff check . |
style/import errors |
| typecheck | mypy skill_vault |
type errors |
| format-check | ruff format --check . |
not formatted |
| test | pytest |
behaviour broken |
Keep the gate fast — it runs on every commit. Run test as its own job so it can
cache longer and fail independently. Add a coverage threshold (pytest-cov --cov-fail-under=85) so regressions also block.
Caching dependencies
- uses: actions/cache@v4
with:
path: ~/.cache/pip
key: ${{ runner.os }}-pip-${{ hashFiles('pyproject.toml') }}
What ships with it
2 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.
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.
- 3d ago First seen · 115 lines · 29 tokens per session scan A 7c270e5faec0
github-actions-ci is a skill published in the GitHub repository vikasudasi/skill-vault (0 stars, last pushed 18d ago), licensed Apache-2.0. It adds 29 tokens to every session and 1,012 once invoked, about $0.0001 per session on Opus 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
github-actions-docs
GitHub Actions — workflows, events, jobs, runners, contexts, expressions, secrets, caching, reusable workflows.
github-workflows
Use when doing GitHub work end-to-end: auth, repository setup, issue triage, PR implementation, code review, CI monitoring, merge/release, and fallback REST workflows.
github-workflow-automation
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management.
ci-cd-pipeline
Design and implement CI/CD pipelines for automated testing and deployment.
claudeconf
Set up or harden a project's quality and security pipeline — git hooks, CI, tests, and pre-merge gates. Researches and pins tools that fit the project's stack instead of using fixed choices, then wires a standard-tool harness you own. Use when initializing a repo, adding CI or pre-commit checks, hardening an existing…
ci-cd-pipeline
Create and optimize CI/CD pipelines with GitHub Actions, automated testing, deployment, and release workflows. Use when setting up continuous integration, deployment automation, or improving build pipelines.