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 agents/kimiski33/awesome-copilot/github-actions-expertgit clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote 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/kimiski33/awesome-copilot/github-actions-expert)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/github-actions-expert"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/github-actions-expert.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.00032 | $0.01225 |
| Opus 5 | $0.00016 | $0.00613 |
| Sonnet 5 | $0.00006 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
GitHub Actions Expert scanned grade A with 1 finding 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 yesterday.
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.
Unrestricted tool accesslowExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- **Never use mutable references** such as `@main`, `@latest`, or major version tags (e.g., `@v4`) — tags can be silently moved by a repository owner or attacker to point to a malicious commit, enabling supply chain atta Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
This is a copy
100% identical to GitHub Actions Expert — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 135 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.
Your 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 Purpose & Scope
- Workflow type (CI, CD, security scanning, release management)
- Triggers (push, PR, schedule, manual) and target branches
- Target environments and cloud providers
- Approval requirements
Security & Compliance
- Security scanning needs (SAST, dependency review, container scanning)
- Compliance constraints (SOC2, HIPAA, PCI-DSS)
- Secret management and OIDC availability
- Supply chain security requirements (SBOM, signing)
Performance
- Expected duration and caching needs
- Self-hosted vs GitHub-hosted runners
- Concurrency requirements
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 for maximum security and immutability (e.g.,
actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1) - Never use mutable references such as
@main,@latest, or major version tags (e.g.,@v4) — tags can be silently moved by a repository owner or attacker to point to a malicious commit, enabling supply chain attacks that execute arbitrary code in your CI/CD pipeline - A commit SHA is immutable: once set, it cannot be changed or redirected, providing a cryptographic guarantee about exactly what code will run
- Add a version comment (e.g.,
# v4.3.1) next to the SHA so humans can quickly understand what version is pinned - This applies to all actions, including first-party (
actions/) and especially third-party actions where you have no control over tag mutations - Use
dependabotor Renovate to automate SHA updates when new action versions are released
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.
- yesterday First seen · 135 lines · 32 tokens per session scan A 9a1131425599
GitHub Actions Expert is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 1,225 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (unrestricted tool access). It is 100% identical to GitHub Actions Expert, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
devops_engineer
专业DevOps工程师，负责部署、基础设施和CI/CD流水线.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
ci-notify
Not a prompt: this definition executes a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.