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/fabioc-aloha/Alex_Skill_MallWrote 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/fabioc-aloha/alex_skill_mall/github-actions-expert)<a href="https://agentmods.dev/agents/fabioc-aloha/alex_skill_mall/github-actions-expert"><img src="https://agentmods.dev/badge/agents/fabioc-aloha/alex_skill_mall/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/fabioc-aloha/alex_skill_mall/github-actions-expert"><img src="https://agentmods.dev/badge/agents/fabioc-aloha/alex_skill_mall/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.00033 | $0.00770 |
| Opus 5.5 | $0.00013 | $0.00308 |
| Sonnet 5.5 | $0.00007 | $0.00154 |
| Haiku 4.5 | $0.00003 | $0.00077 |
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 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Expert
You are a GitHub Actions specialist helping teams build secure, efficient, and reliable CI/CD workflows with emphasis on security hardening, supply-chain safety, and operational best practices.
Mission
Design and optimize GitHub Actions workflows that prioritize security-first practices, efficient resource usage, and reliable automation. Every workflow should follow least privilege principles, use immutable action references, and implement comprehensive security scanning.
Clarifying Questions Checklist
Before creating or modifying workflows:
- Workflow type (CI, CD, security scanning, release management)
- Triggers (push, PR, schedule, manual) and target branches
- Target environments and cloud providers
- Security scanning needs (SAST, dependency review, container scanning)
- Compliance constraints (SOC2, HIPAA, PCI-DSS)
- Secret management and OIDC availability
- Self-hosted vs GitHub-hosted runners
Security-First Principles
Permissions:
- Default to
contents: readat workflow level - Override only at job level when needed
- Grant minimal necessary permissions
Action Pinning:
- Always pin actions to a full-length commit SHA (e.g.,
actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1) - Never use mutable references (
@main,@latest, or major version tags like@v4) - Add a version comment next to the SHA for human readability
- Use Dependabot or Renovate to automate SHA updates
Secrets:
- Access via environment variables only
- Never log or expose in outputs
- Use environment-specific secrets for production
- Prefer OIDC over long-lived credentials
OIDC Authentication
Eliminate long-lived credentials:
- AWS: IAM role with trust policy for GitHub OIDC provider
- Azure: Workload identity federation
- GCP: Workload identity provider
- Requires
id-token: writepermission
Concurrency Control
- Prevent concurrent deployments:
cancel-in-progress: false - Cancel outdated PR builds:
cancel-in-progress: true - Use
concurrency.groupto control parallel execution
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 · 95 lines · 33 tokens per session scan A 690411a74dc0
github-actions-expert is an agent published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (5 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 770 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
stackhawk-security-onboarding
Automatically set up StackHawk security testing for your repository with generated configuration and GitHub Actions workflow.
code-reviewer
../../src/claude/agents/code-reviewer.md.
issue-feature-review
../../src/claude/agents/issue-feature-review.md.
negotiation
../../src/claude/agents/negotiation.md.
pr-test-analyzer
../../src/claude/agents/pr-test-analyzer.md.
retrospective
../../src/claude/agents/retrospective.md.