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/d-oit/rust-2026-template/verify-actionsnpx skills add d-oit/rust-2026-template --skill verify-actionsgit clone --depth 1 https://github.com/d-oit/rust-2026-templateWrote 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/d-oit/rust-2026-template/verify-actions)<a href="https://agentmods.dev/skills/d-oit/rust-2026-template/verify-actions"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/verify-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.00055 | $0.01397 |
| Opus 5 | $0.00028 | $0.00698 |
| Sonnet 5 | $0.00011 | $0.00279 |
| Haiku 4.5 | $0.00006 | $0.00140 |
Grade A, and why
verify-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 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Actions
When to Use
- User asks for this skill's functionality
Never trust version comments in workflow files. Always verify the correct SHA against the actual upstream release before pinning or updating an action.
Why This Matters
- Comments like
# v4can be wrong — a SHA may actually point to v3 or a branch - Version mismatches across workflows cause subtle bugs (e.g., upload-artifact v4 can't download v7 artifacts)
- Supply-chain attacks target CI — pinning a wrong SHA from
maininstead of a tag defeats the purpose
Agent Workflow
1. Before Changing Any Action Reference
When you encounter a uses: owner/action@SHA # vX line, verify the SHA:
For GitHub Actions:
# Look up what tag a SHA belongs to
gh api repos/{owner}/{repo}/git/ref/tags/{tag} --jq '.object.sha'
# Or list recent tags to find the right one
gh api repos/{owner}/{repo}/tags --jq '.[].name' | head -20
# Verify a specific SHA matches a tag
gh api repos/{owner}/{repo}/git/ref/tags/v4 --jq '.object.sha'
For GitLab Actions (CI/CD):
# Check the registry or project for the correct image tag
# Use the project API or container registry
glab api projects/{id}/repository/tags
Fallback — web fetch:
WebFetch: https://github.com/{owner}/{repo}/releases/tag/{tag}
Confirm the release exists and note the commit SHA.
2. Version Consistency Check
Before committing workflow changes, verify ALL action references across the workspace are version-consistent:
# Find all action references and group by action name
grep -rn 'uses:' .github/workflows/ .github/actions/ \
| sed 's/.*uses: \([^@]*\)@.*/\1/' \
| sort | uniq -c | sort -rn
# For each unique action, verify all SHAs match
grep -rn 'uses: actions/upload-artifact@' .github/workflows/
grep -rn 'uses: actions/checkout@' .github/workflows/
grep -rn 'uses: actions/download-artifact@' .github/workflows/
3. When Adding a New Action
- Find the latest release tag from the upstream repo
- Resolve the SHA for that tag using
gh api - Pin the SHA with a version comment
- Verify no other workflow uses a different version of the same action
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.
- 3d ago First seen · 142 lines · 55 tokens per session scan A 1360afe2ed57
verify-actions is a skill published in the GitHub repository d-oit/rust-2026-template (10 stars, last pushed 4d ago), licensed MIT. It adds 55 tokens to every session and 1,397 once invoked, about $0.0003 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
argot-setup-ci
Wire argot into a repository's GitHub Actions as a non-blocking configured check on every pull request — a job summary plus code-scanning annotations. Use when the user wants argot "in CI", "on PRs", "as a GitHub Action", or asks to "set up argot CI". Distinct from argot-setup (local checking) and argot-review-pr…
fixing
Diagnose why a PR's CI failed — compare the CI definition against the sandbox, classify the failure, and make the minimal repair. Use when a PR is red and you must work out why before changing anything.
codebase-argus
Portable Codebase Argus agent playbook for evidence-first multi-agent review of GitHub pull requests, CI failures, GitHub Actions logs, GitHub App webhook review, /argus PR comment commands, autofix branch planning, OpenAI/Claude/Gemini/Codex provider tribunals, downstream merge/rebase work, and long-lived fork sync…
check
Run the full local quality gate (prek hooks + tox test matrix) before committing or opening a pull request. Use when asked to "check", "lint", "run CI locally", or verify a change is ready.
gh-bootstrap
Initialize GitHub repository configuration from vetted upstream templates. Use when setting up repository automation, issue and PR templates, CI workflows, or baseline GitHub project files for a new or existing repo.
container-image-hardening
Context: Pre-publish hardening steps for a new Dockerfile + GitHub Actions workflow. Apply before the first real image publish so the baseline is clean.