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 fmind/dotfiles --skill github-actionsgit clone --depth 1 https://github.com/fmind/dotfilesWrote 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/fmind/dotfiles/github-actions)<a href="https://agentmods.dev/skills/fmind/dotfiles/github-actions"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/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/fmind/dotfiles/github-actions"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/github-actions.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00043 | $0.01472 |
| Opus 5.5 | $0.00017 | $0.00589 |
| Sonnet 5.5 | $0.00009 | $0.00294 |
| Haiku 4.5 | $0.00004 | $0.00147 |
Grade A, and why
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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions CI/CD Standard
Canonical CI/CD workflows for GitHub repositories. The CI workflow delegates to the canonical mise all task, which composes format, check, test, and build from the same tasks used by local lefthook hooks. The CD workflow provides templates for building and deploying applications based on the project's language stack.
Principles
- Single canonical gate: CI runs
mise run all; that task composes the same format, check, and test tasks used by local pre-commit/pre-push hooks plus the production build. Driving both from one mise task set eliminates drift between local checks and CI; workflow syntax and first-party skill contracts belong insidecheck, not in parallel CI-only steps. - Workflows are linted too: a
check:actionstask runsactionlint(correctness: workflow schema, expression types,shellcheckonrun:scripts) andzizmor(security: template injection, credential persistence, cache poisoning, unpinned actions), so workflow regressions fail the same gate as code. zizmor runs offline by default, so the task needs no GitHub token; zizmor.yml relaxes its hash-pin default to the tag-pinning policy from upgrade-tools. - Tools from
mise.toml:jdx/mise-actioninstalls and caches the project toolchain, ensuring that the CI runner runs the identical tool versions pinned locally. - Least privilege: Default to
permissions: contents: read; widen permissions (likepackages: writeorid-token: write) only where needed in deployment jobs. - OIDC & Trusted Publishing: Prefer OpenID Connect (OIDC) for keyless container signing (via
cosign) and package publishing (via PyPI Trusted Publishing), eliminating long-lived credentials. - Downcased registry paths: Dynamically sanitize and downcase repository references to prevent push failures to case-sensitive container registries.
- Fail fast, cancel stale: Concurrency settings cancel superseded runs on pull requests and feature branches automatically while preserving runs on the main branch.
- Clean-state verification: CI asserts an empty porcelain status (
test -z "$(git status --porcelain)") after formatting and generation so both tracked modifications and untracked artifacts fail the build. - Latest Actions: Keep GitHub Actions dependencies up-to-date (e.g.,
actions/checkout@v7,jdx/mise-action@v4).
What ships with it
4 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.
- 1mo ago First seen · 58 lines · 43 tokens per session scan A 15f5d6c23913
github-actions is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,472 once invoked, about $0.0002 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
full-review
Full review: read every repo area, apply verified fixes, and prove all checks pass.
mise
Manage mise tool pins, lockfiles, environments, and tasks shared by hooks and CI.
github-actions
Build GitHub Actions CI/CD and agentic workflows; Dependabot, Lefthook, and zizmor audits.
duckdb
Query and export CSV, Parquet, JSON, or SQLite data with DuckDB.
observability
Instrument Python services and agents: structlog logs, OpenTelemetry traces and metrics.
resolve-conflicts
Resolve Git merge or rebase conflicts by both sides' intent; verify the result.