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/xiaolai/vmark/workflow-auditnpx skills add xiaolai/vmark --skill workflow-auditgit clone --depth 1 https://github.com/xiaolai/vmarkWhat 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.00039 | $0.02477 |
| Opus 5 | $0.00019 | $0.01239 |
| Sonnet 5 | $0.00008 | $0.00495 |
| Haiku 4.5 | $0.00004 | $0.00248 |
Grade A, and why
workflow-audit 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 2d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Audit
Comprehensive audit of .github/workflows/*.yml files against GitHub Actions
best practices, security hardening guidelines, and project conventions.
When to Use
- User asks to audit, review, or check workflows
- Before committing changes to any workflow file
- After a workflow failure that needs root-cause analysis
- Periodic health check (e.g., monthly)
Workflow
- Discover — Glob
.github/workflows/*.ymland list all workflow files. - Parse — Read each file; validate YAML syntax.
- Audit — Run every check in the checklist below against each file.
- Cross-check — Run cross-workflow consistency checks.
- Report — Output a findings table sorted by severity (critical > high > medium > low).
- Fix offer — For each finding, suggest a concrete fix (diff or instruction).
Audit Checklist
1. YAML Validity
- File parses as valid YAML.
- No duplicate keys at the same level.
- No tabs (GitHub Actions requires spaces).
2. Action Version Currency
Check every uses: line.
| Pattern | Severity | Rule |
|---|---|---|
actions/checkout@v4 or lower |
critical | Upgrade to @v6. Node.js 20 actions break June 2, 2026 (forced to Node 24). |
actions/setup-node@v4 or lower |
critical | Same — upgrade to @v6. |
actions/cache@v3 or lower |
high | Upgrade to @v4. |
pnpm/action-setup@v3 or lower |
high | Upgrade to @v4. |
softprops/action-gh-release@v1 |
medium | Upgrade to @v2. |
actions/upload-pages-artifact@v2 or lower |
medium | Upgrade to @v3. |
actions/deploy-pages@v3 or lower |
medium | Upgrade to @v4. |
Any @main or @master pin |
high | Pin to a tag or SHA — mutable refs are a supply-chain risk. |
Node.js deprecation timeline (reference for findings):
- June 2, 2026: Node 24 becomes default (
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=trueto opt in early). - Fall 2026: Node 20 removed entirely from runners.
- Temporary opt-out after June 2:
ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true(stops working fall 2026).
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.
- 2d ago First seen · 203 lines · 39 tokens per session scan A 9862b8f81a60
workflow-audit is a skill published in the GitHub repository xiaolai/vmark (544 stars, last pushed 2d ago), licensed ISC. It adds 39 tokens to every session and 2,477 once invoked, about $0.0002 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-30.
Other skills, from other repositories
deploy-release-test
Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the teste2edeployrelease.yml GitHub Actions workflow. Use only when asked to run the full deploy test suite or this workflow specifically from an internal vercel/next.js PR branch. Do not use for…
ci
A specialized skill for Gemini CLI that provides high-performance, fail-fast monitoring of GitHub Actions workflows and automated local verification of CI failures. It handles run discovery automatically—simply provide the branch name.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
playwright-devops
DevOps workflows for Playwright - CI failure analysis, workflow debugging, and release operations.
fixing-streamlit-ci
Analyze and fix failed GitHub Actions CI jobs for the current branch/PR. Use when CI checks fail, PR checks show failures, or you need to diagnose lint/type/test errors and verify fixes locally.
triage-ci-flake
Use when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing tests.