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/tony/skills/bumping-github-actionsnpx skills add tony/skills --skill bumping-github-actionsgit clone --depth 1 https://github.com/tony/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/tony/skills/bumping-github-actions)<a href="https://agentmods.dev/skills/tony/skills/bumping-github-actions"><img src="https://agentmods.dev/badge/skills/tony/skills/bumping-github-actions.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.00036 | $0.01264 |
| Opus 5 | $0.00018 | $0.00632 |
| Sonnet 5 | $0.00007 | $0.00253 |
| Haiku 4.5 | $0.00004 | $0.00126 |
Grade A, and why
bumping-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 yesterday.
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.
This is a copy
89% identical to github-actions-bumping-github-actions — 17 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bumping GitHub Actions
Audit uses: pins, research each upgrade against real release notes,
land one commit per action, and close dependabot's pull requests by
citing the commit that superseded them.
Two reference files carry the parts that must not drift between this skill and the plugin's commands:
../../references/action-pinning.md— inventory, tag verification, annotated-tag dereferencing, pin granularity, and the per-repo gates to check before claiming an upgrade is safe.../../references/dependabot-closeout.md— the one-way citation rule, the closing protocol, CI attribution, and scope discipline.
Core principle
Verify the target tag exists before writing it. Everything else in this procedure is recoverable; a pin naming a tag that does not resolve breaks every workflow that references it, in every repo, at once.
Scope
Own repositories only. Ownership by account name is not enough — a fork you own is still someone else's project, and its workflows belong upstream. Check whether the repository is a fork and skip it unless the user says otherwise.
Phase 1 — Inventory
Discover repositories with workflows, resolve each one's default
branch, and read every uses: line from that branch. Follow the
inventory section of the pinning reference, including its
word-splitting warning: a naive loop silently drops repos with more
than one workflow file and reports the fleet as clean.
Record, per pin: repository, default branch, file, action, and current version. That table is the unit of work for the rest of the procedure.
Phase 2 — Resolve and verify
For each distinct action, resolve the latest version, choose a target that preserves the repository's existing pin shape, and confirm the target tag exists. Dereference annotated tags before comparing two of them. All four steps are in the pinning reference.
Nothing proceeds past this phase on an unverified tag.
Phase 3 — Research each upgrade
For every distinct upgrade chain, gather the exact latest version, every major release between the current pin and the target with a real release URL, the breaking changes, and what the consuming workflows must actually change. Use web search and the vendor's own release notes; fan out one researcher per chain when there are many.
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.
- yesterday First seen · 149 lines · 36 tokens per session scan A 273825a9c874
bumping-github-actions is a skill published in the GitHub repository tony/skills (2 stars, last pushed 6d ago), licensed MIT. It adds 36 tokens to every session and 1,264 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to github-actions-bumping-github-actions, differing in 17 lines, and is treated as a copy.
Other skills, from other repositories
devops-engineer
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing…
postgres-database-migration
Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases. Trigger when user asks to: Test a schema migration before applying it to production Add, remove, or rename columns safely on a live table Change a column's data…
design-postgis-tables
Comprehensive PostGIS spatial table design reference covering geometry types, coordinate systems, spatial indexing, and performance patterns for location-based applications.
setup-timescaledb-hypertables
Use this skill when creating database schemas or tables for Timescale, TimescaleDB, TigerData, or Tiger Cloud, especially for time-series, IoT, metrics, events, or log data. Use this to improve the performance of any insert-heavy table. Trigger when user asks to: Create or design SQL schemas/tables AND…
migrate-postgres-tables-to-hypertables
Use this skill to migrate identified PostgreSQL tables to Timescale/TimescaleDB hypertables with optimal configuration and validation. Trigger when user asks to: Migrate or convert PostgreSQL tables to hypertables Execute hypertable migration with minimal downtime Plan blue-green migration for large tables Validate…
pgvector-semantic-search
Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…