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 rlespinasse/agent-skills --skill pin-github-actionsgit clone --depth 1 https://github.com/rlespinasse/agent-skillsWrote 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/rlespinasse/agent-skills/pin-github-actions)<a href="https://agentmods.dev/skills/rlespinasse/agent-skills/pin-github-actions"><img src="https://agentmods.dev/badge/skills/rlespinasse/agent-skills/pin-github-actions/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/rlespinasse/agent-skills/pin-github-actions"><img src="https://agentmods.dev/badge/skills/rlespinasse/agent-skills/pin-github-actions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 270 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.00092 | $0.02957 |
| Opus 5.5 | $0.00037 | $0.01183 |
| Sonnet 5.5 | $0.00018 | $0.00591 |
| Haiku 4.5 | $0.00009 | $0.00296 |
Grade A, and why
pin-github-actions 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 5d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pin GitHub Actions to Commit SHAs
You are helping the user migrate their GitHub Actions workflows from tag-based references
(e.g., actions/checkout@v4) to commit SHA-pinned references with version comments
(e.g., actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.7).
This prevents supply-chain attacks where a tag can be moved to point to malicious code.
Step 1: Discover Workflows and Current State
-
Find all workflow files:
find .github/workflows -name '*.yml' -o -name '*.yaml' -
Extract all
uses:references from each workflow file -
Check for an existing Dependabot configuration at
.github/dependabot.ymlor.github/dependabot.yaml -
Check for git submodules (
.gitmodules) and other dependency ecosystems (e.g.,package.json,go.mod,Gemfile) that Dependabot could manage
Present a summary table of the current state:
| Action | Workflow | Current Ref | Pinned? |
| ----------------------------------- | --------------------- | ----------- | ------- |
| actions/checkout | build.yaml | @v4 | No |
| docker/build-push-action | build.yaml | @abc123... | Yes |
Step 2: Resolve Latest Releases
Already-Pinned Repositories
If all actions are already SHA-pinned (40-character hex refs with version comments), present the current state table and ask the user:
All actions are already pinned to commit SHAs. Would you like to check for available updates?
- If the user declines, skip directly to Step 4 (Dependabot configuration)
- If the user accepts, proceed with batch resolution below to check all actions at once
For repositories with a mix of pinned and unpinned actions, resolve only the unpinned ones — but offer to check pinned actions for updates as well.
Security: Handling Third-Party API Responses
GitHub API responses contain untrusted content from public repositories. To prevent indirect prompt injection:
What ships with it
1 file 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.
- 5d ago Changed · +1 lines · +23 tokens per session a8010dbe72eb
- 1mo ago First seen · 286 lines · 69 tokens per session scan A 751f9e47a116
pin-github-actions is a skill published in the GitHub repository rlespinasse/agent-skills (13 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 2,957 once invoked, about $0.0004 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
deploy-checklist
Pre-deploy and post-deploy checklist skill. Ensures env vars, migrations, CI, rollback plan, smoke tests, and monitoring are verified before and after every deployment.
kubestellar-console
Multi-cluster Kubernetes dashboard with AI-powered operations via MCP server and 10+ built-in agent skills.
agentic-actions-auditor
Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches. AI agents running in CI/CD pipelines.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.
ci-cd
Automates CI/CD pipeline setup. Enforces unskippable quality gates, shift-left static analysis, secret scanning, and hardened GitHub Actions workflows.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.