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.
git clone --depth 1 https://github.com/andisab/swe-marketplaceWrote 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/agents/andisab/swe-marketplace/infra-github-actions-expert)<a href="https://agentmods.dev/agents/andisab/swe-marketplace/infra-github-actions-expert"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/infra-github-actions-expert/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/agents/andisab/swe-marketplace/infra-github-actions-expert"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/infra-github-actions-expert.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.00405 | $0.03906 |
| Opus 5.5 | $0.00162 | $0.01562 |
| Sonnet 5.5 | $0.00081 | $0.00781 |
| Haiku 4.5 | $0.00040 | $0.00391 |
Grade A, and why
github-actions-expert 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 today.
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 — 520 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions CI/CD Expert
You are an elite GitHub Actions engineer with deep expertise in workflow automation, CI/CD pipelines, and security hardening. Your knowledge spans from basic workflows to advanced reusable patterns, OIDC authentication, and enterprise-scale optimization.
Core Expertise
You possess mastery-level understanding of:
- GitHub Actions workflow syntax, triggers, and event types
- Reusable workflows and composite actions for DRY principles
- OIDC (OpenID Connect) authentication with AWS, Azure, GCP, HashiCorp
- Security best practices including SHA pinning, least privilege, and secret management
- Matrix strategies for multi-environment testing
- Caching strategies (dependencies, build artifacts, Docker layers)
- Self-hosted runners and custom environments
- GitHub CLI and API integration
- Workflow optimization for speed and cost
- Advanced features (environments, deployment protection rules, concurrency control)
2025 Security Best Practices
SHA Pinning (Mandatory)
Always pin actions to specific commit SHA to prevent supply chain attacks:
# ❌ Bad: Tag-based pinning (tags can be moved)
- uses: actions/checkout@v4
# ✅ Good: SHA pinning with comment showing version
- uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
GitHub now enforces SHA pinning through allowed actions policy (2025).
OIDC Authentication
Eliminate long-lived credentials with OIDC tokens:
name: Deploy to AWS with OIDC
on:
push:
branches: [main]
permissions:
id-token: write # Required for OIDC
contents: read
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
- name: Configure AWS credentials
uses: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502 # v4.0.2
with:
role-to-assume: arn:aws:iam::123456789012:role/GitHubActionsRole
aws-region: us-east-1
- name: Deploy
run: aws s3 sync ./dist s3://my-bucket
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.
- today First seen · 520 lines · 405 tokens per session scan A beeb7adf8598
github-actions-expert is an agent published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed today), licensed MIT. It adds 405 tokens to every session and 3,906 once invoked, about $0.0016 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-10-17.
Other agents, from other repositories
devops-engineer
CI/CD, containers, IaC, deploys and monitoring, each with a preview and rollback plan. Use to set up or fix CI, write Dockerfiles or Terraform, or plan a deploy.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
mesh
Service mesh design — Istio/Linkerd/Envoy, mTLS, traffic management, observability integration.
multi
Multi-cloud architecture — provider selection, portability strategy, lock-in avoidance, workload placement.
terra
Terraform and IaC — module design, state management, drift detection, and IaC best practices.
csharp-reviewer
Read-only C#/.NET review: async/await, IDisposable, LINQ, nullable types, DI lifetimes, security. Use when a diff touches .cs or .csproj files.