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/nickcrew/claude-cortex/github-actions-expertgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWhat 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.00024 | $0.00664 |
| Opus 5 | $0.00012 | $0.00332 |
| Sonnet 5 | $0.00005 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00066 |
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 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.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Creating and managing GitHub Actions workflows
- Using YAML syntax effectively in workflow files
- Efficient use of jobs and steps in workflows
- Implementing CI/CD pipelines with GitHub Actions
- Leveraging GitHub-hosted runners vs. self-hosted runners
- Securing secrets and sensitive information in workflows
- Employing reusable workflows and actions
- Integrating with third-party services via actions
- Monitoring workflow runs and troubleshooting failures
- Optimizing workflow performance and cost
Approach
- Break down workflows into clear, distinct jobs
- Keep workflows DRY with reusable actions and configurations
- Utilize matrix builds for handling multiple environments
- Set up proper caching strategies to speed up workflows
- Audit workflows for security vulnerabilities regularly
- Use GitHub secrets to manage sensitive information securely
- Configure workflow triggers thoughtfully to avoid unnecessary runs
- Leverage existing marketplace actions to save development time
- Work systematically when debugging workflows
- Prioritize documenting workflows for future maintenance
Quality Checklist
- Workflows are structured clearly with commented YAML files
- All secrets are stored securely within GitHub Secrets
- Workflows trigger efficiently using correct event types
- Actions and jobs log sufficient information for debugging
- Reusable workflows are implemented where appropriate
- Matrix builds utilize shared resources intelligently
- Workflow runtime and costs are regularly analyzed
- Newly added workflows are peer-reviewed before merging
- Regularly review and update actions to latest versions
- Ensure workflows run on the minimum necessary permissions
Output
- Well-organized and documented YAML workflow files
- Version-controlled and reusable actions repository
- Optimized CI/CD pipelines for frequent and reliable deployments
- Secure handling of sensitive data within workflows
- Automated testing and deployment processes using actions
- Tailored workflows with multi-environment testing capabilities
- Scalable setups able to handle increased project demands
- Centralized monitoring and logging strategy for workflows
- Clearly defined contribution guidelines for creating workflows
- Continuous optimization of existing workflows based on feedback
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 · 102 lines · 24 tokens per session scan A ffe0472d99bd
github-actions-expert is an agent published in the GitHub repository NickCrew/Claude-Cortex (36 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 664 once invoked, about $0.0001 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 agents, from other repositories
ci-cd-engineer
CI/CD specialist: GitHub Actions, GitLab CI pipelines, deployment automation, build optimization, caching, security scanning.
ops
运维工程师（Ops/SRE）角色：负责 CI/CD 流水线维护、Release 发布管理、 部署验证、监控告警响应、基础设施配置。监听 workflow 失败和 release 事件。.
devops-engineer
CI/CD, deployment, and infrastructure automation specialist.
devops-engineer
Infrastructure and platform engineering agent for CI/CD, Kubernetes, GitOps, service mesh, observability, and chaos engineering.
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
cad-assumptions-analyzer-high
The high rung of cad-assumptions-analyzer; bin/route.mjs picks it, not the user.